12:05 p.m.
Dear Fedora CoreOS Community
I did have FCOS installed on multiple Intel NUCs for a long time and was always very
happy. Being on board since CentOS Atomic Host, Fedora CoreOS really is an outstandig
product, thank you so much for making this possible.
Now to the issue:
My current system (NUC8i5BEK) has a Zincati maintenance window defined and after updates
reboots automatically during this time window. Unfortunately, since release
35.20220116.3.0, it seems that networking does not come up reliably after a reboot. The
boot process gets stuck and the system does not request an IP from the DHCP. (Somehow
sounded a bit like https://github.com/coreos/fedora-coreos-tracker/issues/1066 but my
network driver "e1000e" is different)
I identified two workarounds:
- physically access the system and select at boot loader menu the last working release
(~rollback)
- reboot multiple times, sometimes networking magically comes up
Last working release: 35.20220103.3.0 -> please note that this release always boots the
first time even as of today
Not working releases: 35.20220116.3.0, 35.20220131.3.0, 35.20220213.3.0
Could you please share any guidance how I could proceed? Provide more technical details
here in the mailing list? Or opening a bug at
https://github.com/coreos/fedora-coreos-tracker?
Thanks in advance for any feedback,
Beat