03:08 <quentin9696[m]> Hi !... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/01abbe3faf360acb5c42505872f2ee65cbcf688f>)

03:09 <quentin9696[m]> do you have any clue on where I can search ?

16:40 <travier[m]> quentin9696: This looks like something from he host. Can you make a post on the forum with more context and post the link here?

17:10 <travier[m]> heads up: https://github.com/fedora-silverblue/issue-tracker/issues/400 might impact FCOS but not sure

17:10 <travier[m]> See the linked BZs

17:11 <dustymabe> travier[m]: fallout from https://github.com/coreos/fedora-coreos-tracker/issues/186#issuecomment-1372867008 ?

17:13 <travier[m]> OK, so it's "us" breaking others :/

17:13 <travier[m]> So we should be good

17:14 <dustymabe> well yeah, it's complicated I guess. the default dep was dropped and so it would require others to name it

17:14 <dustymabe> does silverblue installed weak deps?

17:15 <dustymabe> could be added back as a weak dep

17:16 <dustymabe> https://src.fedoraproject.org/rpms/libpwquality/blob/rawhide/f/libpwquality.spec#_15

17:17 <dustymabe> i guess suggests is weaker than recommends

17:18 <dustymabe> looks like it will probably be added back as a recommends: https://bugzilla.redhat.com/show_bug.cgi?id=2158891#c4

17:19 <travier[m]> I think it should be a recommends

17:20 <dustymabe> WFM

17:23 <jlebon> i don't see a `recommends: false` so it should pull it in, yeah

17:24 <jaimelm> dustymabe, travier[m] Anything for the OKD Working Group meeting? (happening now)

17:24 <travier[m]> Sorry, I can't join

17:25 <travier[m]> jaimelm: ^^

17:25 <jaimelm> No worries. Anything to mention?

17:25 <dustymabe> jaimelm: I don't have anything

17:25 <jaimelm> OK< thanks

17:25 <travier[m]> I don't have anything either. Is there an item on the agenda on disabling reporting bugs via Bugzilla?

17:26 <jaimelm> No

17:26 <travier[m]> OK, then this basically says it all. We're asking if the community is fine if we stop using Bugzilla for reporting bugs and only use GitHub or later the OKD Jira project

17:30 <jaimelm> Got it. Will pose the question.

17:32 <travier[m]> Thanks!

17:32 <dustymabe> jaimelm++

17:32 <zodbot> dustymabe: Karma for jaimelm changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any

18:59 <hcosta[m]> I’am sorry maybe I still don’t quite grasp the mechanics of core os, I two questions maybe can some clarify.

18:59 <hcosta[m]> 1. From I what I have read /var and /etc will persist when updating/rebooting, so this could be used for persist storage when using a container engine, my assumption is that I can also attach an extra disk and mount it somewhere inside /var for example /var/data.

18:59 <hcosta[m]> 2. How does fcos handles major upgrades for example 37 to 38, the de host need to be redeployed?

18:59 <hcosta[m]> Thanks in advance all.

19:00 <hcosta[m]> * I’am sorry maybe I still don’t quite grasp the mechanics of core os, I have two questions maybe can some clarify.

19:00 <hcosta[m]> 1.From I what I have read /var and /etc will persist when updating/rebooting, so this could be used for persist storage when using a container engine, my assumption is that I can also attach an extra disk and mount it somewhere inside /var for example /var/data.

19:00 <hcosta[m]> 2.How does fcos handles major upgrades for example 37 to 38, the de host need to be redeployed?

19:00 <hcosta[m]> Thanks in advance all.

19:01 <hcosta[m]> * I’am sorry maybe I still don’t quite grasp the mechanics of core os, I have two questions maybe can some clarify.
1. From I what I have read /var and /etc will persist when updating/rebooting, so this could be used for persistent storage when using a container engine, my assumption is that I can also attach an extra disk and mount it somewhere inside /var for example /var/data.
2. How does fcos handles major upgrades for

19:01 <hcosta[m]> example 37 to 38, the de host need to be redeployed?
Thanks in advance all.

19:01 <hcosta[m]> * I’am sorry maybe I still don’t quite grasp the mechanics of core os, I have two questions maybe can some clarify.
1. From I what I have read /var and /etc will persist when updating/rebooting, so this could be used for persistent storage when using a container engine, my assumption is that I can also attach an extra disk and mount it somewhere inside /var for example /var/data.
2. How does fcos handles major upgrades for

19:01 <hcosta[m]> example 37 to 38, does the host need to be redeployed?
Thanks in advance all.

19:01 <walters> hcosta: correct, `/var` and `/etc` persist, and major version updates are not different.

19:03 <hcosta[m]> So in certain point in time the upgrade mechanism will update from one major version to the following.

19:03 <hcosta[m]> As a regular update.

19:03 <dustymabe> hcosta[m]: yes, if you are following i.e. the `stable` stream. at some point in time your node will automatically upgrade from fedora 37 content to fedora 39 content

19:04 <dustymabe> s/39/38

19:04 <hcosta[m]> Thank you for clarifying that :)

19:04 <hcosta[m]> Awesome

19:10 <dustymabe> np

20:21 <jlebon> ravanel__: are you currently looking at https://github.com/coreos/fedora-coreos-tracker/issues/1373 ? if not, i'll take a look at it

21:02 <dustymabe> jlebon: on qemu this is why we didn't see the failure I think: `nm-initrd.service was skipped because of an unmet condition check (ConditionPathExists=/run/NetworkManager/initrd/neednet)`

21:02 <dustymabe> i.e. the ignition is provided via fw_cfg so networking wasn't initiated

21:14 <jlebon> dustymabe: ahh makes sense

21:14 <dustymabe> i'm going to fix that for at least one of the tests

21:23 <dustymabe> jlebon: so the nm-initrd-generator itself isn't what is creating `lo.nmconnection`

21:23 <dustymabe> it gets created when NM starts up

21:38 <jlebon> dustymabe: ok interesting. i guess we could ignore it when doing the diff in the propagation code, though would be good to sanity-check this is expected behaviour

21:46 <dustymabe> I expect that it is expected behavior

21:46 <dustymabe> i'll open an issue and also work on a patch for the propagation code