Created attachment 1712868 [details] Kernel panic screenshot Created attachment 1712868 [details] Kernel panic screenshot Description of problem: Attempting to PXE boot the latest OpenShift 4.5.7 fails to read the initrd.img with this error message: error: ../../grub-core/net/net.c:1795:timeout 'rhcos-4.5.6-x86-64-installer-initramfs.x86.64.img' after which a kernel panic is produced (please see attached image). How reproducible: Always Actual results: Kernel panic Expected results: System can be installed without issue Additional info: Replacing grub64.efi from an earlier package (OpenShift 4.5.2) fixes the issue and the system can ne installed correctly. From the Release Notes of OpenShift 4.5.7: "Red Hat Enterprise Linux CoreOS upgraded from 45.82.202007141718-0 to 45.82.202008150329-0" Looks very similar to: https://bugzilla.redhat.com/show_bug.cgi?id=1869335 and https://bugzilla.redhat.com/show_bug.cgi?id=1873278
Is it possible to PXE a RHEL 8 host in this environment? RHCOS uses the same `grub` packages (i.e. grub2-common-2.02-87.el8_2) as found in RHEL 8, so I would expect to see the same problem when booting RHEL 8. If you can confirm that RHEL 8 has the same problem, we can engage the RHEL grub team on this issue. This may just be a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1871034
Marking this for an `UpcomingSprint` while we wait for additional information and triage.
Conservatively targeting for 4.7 with a low priority until we receive more information.
(In reply to Micah Abbott from comment #1) > Is it possible to PXE a RHEL 8 host in this environment? RHCOS uses the > same `grub` packages (i.e. grub2-common-2.02-87.el8_2) as found in RHEL 8, > so I would expect to see the same problem when booting RHEL 8. > > If you can confirm that RHEL 8 has the same problem, we can engage the RHEL > grub team on this issue. > > This may just be a dupe of > https://bugzilla.redhat.com/show_bug.cgi?id=1871034 This is indeed a duplicate of Bug #1871034. That's fixed for 8.3, please set zstream? on that BZ if you need the fix also in released versions.
Per comment #5, marking as a duplicate of BZ#1871034 *** This bug has been marked as a duplicate of bug 1871034 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days