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
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos…
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos…
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos…
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:31:30 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-30/fedora_coreos…
.
Meeting summary
---------------
* roll call (dustymabe, 16:31:35)
* Action items from last meeting (dustymabe, 16:35:56)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/601
(davdunc, 16:39:11)
* LINK: https://github.com/amazonlinux/amazon-ec2-utils (davdunc,
16:44:10)
* for #601 after davadunc talked with Amazon engineers the code in
ec2-utils and ec2-net-utils might be a good reference for other
distributions, but is not promised to work. They encourage us to
write our own with those as a reference. (dustymabe, 16:50:52)
* ACTION: jlebon bgilbert travier to discuss potential solutions for
#392 and update the ticket and present the outcome at a future
meeting. (jlebon, 16:53:44)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1147
(miabbott, 16:54:38)
* dustymabe aaradhak ravanelli mnguyen and i met today to lay out the
todo items for f36 test day -
https://github.com/coreos/fedora-coreos-tracker/issues/1147
(miabbott, 16:55:00)
* miabbott sent an email to coreos-status for ovf changes and posted
to the fedora discussion site (miabbott, 16:55:28)
* LINK:
https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedorapro…
(miabbott, 16:55:36)
* LINK:
https://discussion.fedoraproject.org/t/changes-to-vmware-ovf-metadata/37792
(miabbott, 16:55:42)
* supportability of non-EOL VMware platforms (dustymabe, 16:55:53)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1146
(dustymabe, 16:55:57)
* AGREED: FCOS will not make any changes to the hardware version in
the OVF metadata of the VMware OVA that would exclude non-EOL
platforms from being supported. (jlebon, 17:03:27)
* F36 FCOS Test Day TODO List (dustymabe, 17:04:00)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1147
(dustymabe, 17:04:06)
* we have most work items that we identified assigned to volunteers!
(dustymabe, 17:14:58)
* the organizers of the test day are going to get together in an
informal session next Tuesday (April 5) to strategize about what
test cases are left to execute and divide them up. All are welcome
to join. (dustymabe, 17:17:08)
* tracker: Fedora 36 changes considerations (dustymabe, 17:18:48)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/918
(dustymabe, 17:18:52)
* FCOS `next` stream is now based on Fedora 36 beta content
(dustymabe, 17:19:29)
* an issue found so far with Fedora 36 is RPi4 networking seems to not
work: https://github.com/coreos/fedora-coreos-tracker/issues/1145
(dustymabe, 17:20:14)
* another issue found (not filed), but NM dispatchers are blocked by
SELinux: https://bugzilla.redhat.com/show_bug.cgi?id=2065940
(dustymabe, 17:21:16)
* open floor (dustymabe, 17:24:30)
Meeting ended at 17:31:40 UTC.
Action Items
------------
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
Action Items, by person
-----------------------
* bgilbert
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
* jlebon
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (110)
* davdunc (37)
* zodbot (18)
* jlebon (16)
* miabbott (12)
* bgilbert (9)
* fifofonix (5)
* aaradhak[m] (4)
* ravanelli (3)
* skunkerk (3)
* jdoss (2)
* saqali (1)
* aaradhak (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-23/fedora_coreos…
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-23/fedora_coreos…
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-23/fedora_coreos…
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:28:21 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-23/fedora_coreos…
.
Meeting summary
---------------
* roll call (dustymabe, 16:28:26)
* Action items from last meeting (dustymabe, 16:33:21)
* ACTION: davdunc to put a package review in for ec2-net-utils and
brainstorm on how we can use that for #601 (dustymabe, 16:34:59)
* F36: Fedora CoreOS Test Week (dustymabe, 16:35:07)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1123
(dustymabe, 16:35:13)
* ACTION: ravanelli and mnguyen and miabbott to work with dustymabe to
organize the test day for f36. miabbott will attempt to document the
process for future iterations (dustymabe, 16:48:08)
* Drop libvarlink-utils from package set (dustymabe, 16:49:18)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1130
(dustymabe, 16:49:24)
* AGREED: We don't know of any other common uses of libvarlink-utils
on FCOS right now. We'll try removing it from `next` and send an
email about it to the list to see if that gives us any new
information. After a period of time with no issues we'll promote
that to `testing` and `stable`. (dustymabe, 16:58:30)
* Update the VMware metadata to new, modern defaults (dustymabe,
16:59:13)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1119
(dustymabe, 16:59:19)
* because of some great work by bgilbert we now have the flexibility
to use different values in the OVA for FCOS and RHCOS so each
derivative can use values most appropriate. FCOS will remain at hw
version 13 until after the vSphere 6.5/6.7 EOL date. (dustymabe,
17:05:31)
* the defaults were changed for FCOS to use EFI firmware and Secure
Boot by default (dustymabe, 17:06:07)
* LINK:
https://github.com/coreos/coreos-assembler/pull/2762/files#diff-14140576af1…
>SB is not enabled here (travier, 17:11:11)
* ACTION: miabbott to send an email to the list about planned updates
to the OVA (dustymabe, 17:12:21)
* Unable to disable zincati.service using Ignition (dustymabe,
17:13:25)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/392
(dustymabe, 17:13:32)
* there was no response to last week's request for feedback on
https://github.com/systemd/systemd/pull/15205 so we'll pursue a
workaround solution. (dustymabe, 17:16:29)
* ACTION: jlebon bgilbert travier to discuss potential solutions for
#392 and update the ticket and present the outcome at a future
meeting. (dustymabe, 17:25:48)
* open floor (dustymabe, 17:26:34)
Meeting ended at 17:29:26 UTC.
Action Items
------------
* davdunc to put a package review in for ec2-net-utils and brainstorm on
how we can use that for #601
* ravanelli and mnguyen and miabbott to work with dustymabe to organize
the test day for f36. miabbott will attempt to document the process
for future iterations
* miabbott to send an email to the list about planned updates to the OVA
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
Action Items, by person
-----------------------
* bgilbert
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
* davdunc
* davdunc to put a package review in for ec2-net-utils and brainstorm
on how we can use that for #601
* dustymabe
* ravanelli and mnguyen and miabbott to work with dustymabe to
organize the test day for f36. miabbott will attempt to document the
process for future iterations
* jlebon
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
* miabbott
* ravanelli and mnguyen and miabbott to work with dustymabe to
organize the test day for f36. miabbott will attempt to document the
process for future iterations
* miabbott to send an email to the list about planned updates to the
OVA
* mnguyen
* ravanelli and mnguyen and miabbott to work with dustymabe to
organize the test day for f36. miabbott will attempt to document the
process for future iterations
* ravanelli
* ravanelli and mnguyen and miabbott to work with dustymabe to
organize the test day for f36. miabbott will attempt to document the
process for future iterations
* travier
* jlebon bgilbert travier to discuss potential solutions for #392 and
update the ticket and present the outcome at a future meeting.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (105)
* bgilbert (40)
* jlebon (29)
* zodbot (27)
* travier (26)
* miabbott (19)
* mnguyen (6)
* davdunc (5)
* fifofonix (2)
* jbrooks (1)
* skunkerk (1)
* saqali (1)
* aaradhak[m] (1)
* aaradhak (1)
* ravanelli (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
The most recent kernel update to 5.16.13-200.fc35 has been reported
to cause failures for NFS clients connecting to some QNAP NAS systems.
Details of the issue as well as links to upstream forum posts and
downstream bug reports can be found in our issue tracker:
https://github.com/coreos/fedora-coreos-tracker/issues/1121
Fortunately this bug was caught in our `testing` stream. Unfortunately,
we do need to proceed promoting this kernel into our `stable` stream
because the update will fix CVE-2022-0847 (known as "dirty pipe").
If you will be affected by this bug, the easiest workaround is to switch
the mount options for the mount to add `vers=4.0` for NFS 4.0. You can
then follow progress in the tracker issue to know when to revert
the change.
Dusty Mabe for the Fedora CoreOS Team