OCP Version at Install Time: 4.8.9 RHCOS Version at Install Time: https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.8/4.8.2/rhcos-live-rootfs.x86_64.img OCP Version after Upgrade (if applicable): N/A RHCOS Version after Upgrade (if applicable): N/A Platform: baremetal Architecture: x86_64 What are you trying to do? What is your use case? This is a minimal-iso generated by Assisted Installer. We noticed this issue when booting this image on a HPE hardware that had TPM enabled. What happened? What went wrong or what did you expect? The boot option recovery mention appeared, the node was rebooted, but it never progressed into a normal boot. It either went back to the same screen or presented another error. What are the steps to reproduce your issue? Please try to reduce these steps to something that can be reproduced with a single RHCOS node. 1. Go to cloud.redhat.com 2. Create a cluster: https://console.redhat.com/openshift/assisted-installer/clusters/~new 3. Pick any name 4. Pick any domain 5. Select SNO (although this happens in other modes too) 6. Accepted the warning 7. Click next 8. Click Generate the discovery ISO 9. Select minimal 10. Click generate (it should be ~100 MB) (no need to add any keys, unless you really want to) 11. Boot the image 12. Profit (to some definition of profit)
I tried reproducing locally in QEMU, and the system correctly booted once to the Boot Options Restoration screen and the second time to the GRUB menu. I expect the problem is hardware-specific. As a workaround, you should be able to press Enter at the Boot Options Restoration screen and then choose "Always continue boot". The restoration screen is new in shim 15.4, but the automatic reboot has existed for a while. shim 15.4 is in all supported OCP releases, but is currently only in bootimages for OCP 4.8 and up. Could you try booting the same hardware from an official RHCOS 4.7 ISO and report whether the machine boot-loops?
This bug has been reported fixed in a new RHCOS build. Do not move this bug to MODIFIED until the fix has landed in a new bootimage.
Verified the fallback efi is removed on RHCOS 410.84.202110081440-0 live installer. $ sudo mount -o loop,ro rhcos-410.84.202110081440-0-live.x86_64.iso /mnt/iso $ sudo mount -o loop,ro /mnt/iso/images/efiboot.img /mnt/efi $ tree /mnt/efi /mnt/efi └── EFI └── BOOT ├── BOOTX64.EFI ├── fonts ├── grub.cfg ├── grubx64.efi └── mmx64.efi 3 directories, 4 files
The fix for this bug has landed in a bootimage bump, as tracked in bug 2004596 (now in status MODIFIED). Moving this bug to MODIFIED.
Verify fallback efi not found in RHCOS 410.84.202110140201-0 live installer # mount -o loop,ro rhcos-410.84.202110140201-0-live.x86_64.iso /mnt/iso/ # mount -o loop,ro /mnt/iso/images/efiboot.img /mnt/efi # tree /mnt/efi/ /mnt/efi/ └── EFI └── BOOT ├── BOOTX64.EFI ├── fonts ├── grub.cfg ├── grubx64.efi └── mmx64.efi 3 directories, 4 files
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056