Bug 1970514 - UEFI entry not created for /EFI/redhat/shimx64.efi
Summary: UEFI entry not created for /EFI/redhat/shimx64.efi
Keywords:
Status: CLOSED DUPLICATE of bug 1966129
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Tomas Sedovic
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-10 15:44 UTC by Derek Higgins
Modified: 2021-06-11 11:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-11 11:21:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Derek Higgins 2021-06-10 15:44:39 UTC
This bug is to track an ironic workaround for a bug being investigated in shim
https://bugzilla.redhat.com/show_bug.cgi?id=1966129


When deploying a whole disk image, IPA creates a boot entry for for any bootloader it finds on the EFI system partition.

In RHEL (and possibly others) it finds a bootloader in
/boot/EFI/BOOT/BOOTX64.EFI
and creates a boot entry for it

This does not match the entry that RHEL expects to see, RHEL expects an entry pointing to \EFI\redhat\shimx64.efi using a label read from BOOTX64.CSV

BOOTX64.EFI and shimx64.efi are the same file but behave differently depending on their filename and a bug in the shim code is causing it to crash on boot (sometimes) if referenced as \EFI\BOOT\BOOTX64.EFI

IPA should instead find shimx64.efi and create an entry that the OS expects (based on the contents of /boot/efi/redhat/BOOTX64.CSV)

Failing entry
Boot0026* ironic1 HD(2,GPT,3b6e914a-f943-4f30-9f2d-4cb92848d7eb,0x1000,0x3f800)/File(\EFI\BOOT\BOOTX64.EFI)

Expected entry
Boot0024* Red Hat Enterprise Linux HD(2,GPT,3b6e914a-f943-4f30-9f2d-4cb92848d7eb,0x1000,0x3f800)/File(\EFI\redhat\shimx64.efi)

Comment 1 Tomas Sedovic 2021-06-11 11:21:07 UTC
Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1966129. That bug has the full investigation info, the fix and it moved back from RHEL/shim to Ironic.

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


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