--- OCP Version at Install Time: 4.8 RHCOS Version at Install Time: 4.8 Platform: baremetal Architecture: x86_64 HP DL360 Gen 9 What are you trying to do? What is your use case? Booting the machine with rhcos 4.8.2 iso for the HPDL360 Gen 9 machine it fails before stage1 of booting OS boot failure "x64 Exception Type 06 - Invalid Opcode Exception" (screenshot attached) Attaching the screenshots about the machine's hardware. When we boot coreos 4.7.13 iso or rhel 8.4 iso it works fine and we do see the machine booting up propery but does not work with rhcos 4.8 There has been upstream community discussion about the message and the customer has changed the console from html5 to java console but still sees the issue. https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/DL360-Gen9-ESXi/m-p/7124546/highlight/true#M173951 What happened? What went wrong or what did you expect? To reproduce:- 1. Take a HP DL360 Gen9 machine and then boot the machine with rhcos 4.8.2 iso. Attaching the screenshots of machine details and a short video of the error.
We recently fixed some booting issues with the LiveISO so that may be it. Can you test with the latest image from https://releases-rhcos-art.cloud.privileged.psi.redhat.com/?stream=releases/rhcos-4.8 ?
There are two recent fixes to EFI boot; one of the bugs affected 4.7 and one didn't. Since the 4.7 ISO is working, it looks like the problem is in fallback.efi, which has now been removed from the ISO to fix bug 2004677.
(A private comment confirmed that a recent build of the 4.8 ISO is working correctly.)
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.
@bglibert This is the output I get from the latest installer. The fallback.efi is removed but it looks different from the 4.9 installer (missing the EFI/BOOT/redhat, see https://bugzilla.redhat.com/show_bug.cgi?id=2006962#c4). If this is expected, I can move this to Verified: Tested. $ 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
Yup, that's correct. The 4.10 PR did some additional simplification that wasn't included in the backports.
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.
Moving to verified now that the boot image has at bug 2004596 has been verified. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2021-10-25-062528 True False 9m36s Cluster version is 4.10.0-0.nightly-2021-10-25-062528
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