Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1873278 - error: ../../grub-core/net/net.c:1795:timeout reading initrd.img
Summary: error: ../../grub-core/net/net.c:1795:timeout reading initrd.img
Keywords:
Status: CLOSED DUPLICATE of bug 1871034
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.5
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
: 4.7.0
Assignee: Micah Abbott
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-27 18:35 UTC by hocr1
Modified: 2023-12-15 19:03 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-05 12:49:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Kernel panic screenshot (deleted)
2020-08-27 18:35 UTC, hocr1
no flags Details

Description hocr1 2020-08-27 18:35:43 UTC
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

Comment 1 Micah Abbott 2020-09-02 14:50:34 UTC
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

Comment 3 Micah Abbott 2020-09-10 21:04:21 UTC
Marking this for an `UpcomingSprint` while we wait for additional information and triage.

Comment 4 Micah Abbott 2020-09-14 20:06:27 UTC
Conservatively targeting for 4.7 with a low priority until we receive more information.

Comment 5 Javier Martinez Canillas 2020-09-15 13:24:42 UTC
(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.

Comment 6 Micah Abbott 2020-10-05 12:49:15 UTC
Per comment #5, marking as a duplicate of BZ#1871034

*** This bug has been marked as a duplicate of bug 1871034 ***

Comment 7 Red Hat Bugzilla 2023-09-14 06:07:54 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.