After initial build of a UEFI VM using Red Hat Satellite, the system fails to boot up with error "Partition with known EFI file not found" when VM Hardware version is 17 or above
Description of problem:
It's possible to deploy UEFI ( with or without secureboot ) VMs in VMware 7.0 u2 but even if the initial build gets completed, the system never comes up after the final reboot and shows error "Partition with known EFI file not found" as it will not be able to find out the bootloader to boot with.
This problem only happens when the VMs HW version is set to 17 ( ESX 7.0 compatible) or 19 ( ESX 7.0 u2 compatible ).
Version-Release number of selected component (if applicable):
Satellite 6.11 [ Satellite 6.10 and 6.9 are affected as well ]
VMware 7.0 u2
How reproducible:
Always
Steps to Reproduce:
1. Have a VMware 7.0 available and configured.
2. Install a Satellite 6.11 and configure it to deploy systems(rhel 8.6\rhel 9.0) via PXE
3. Create a compute resource in Satellite UI that can help communicating with the VMware 7.0 infra
4. Now, Deploy a RHEL 8.6 or RHEL 9.0 from Satellite using the compute resource and before submitting the build ensure the following were done:
Ram\Memory: 4096 mb
Virtual H\W version: 19 (ESXI 7.0 u2)
HDD\Disk size: 10 GB
Loader in Operating systems page: Grub2 UEFI
5. Submit the host for build and then observe the VMware console to monitor the build process.
6. Repeat Step 4 and 5 for another system build where "Virtual H\W version" is selected as "15 (ESXi 6.7 u2)"
Actual results:
At Step 5:
* Initial system build will be comepleted
* System will be rebooted
* It will start booting from network , get the "Chainload Grub2 EFI from ESP" option to boot from.
* After selecting the same, we get to see bunch of error messages about not able to found the bootloaders and finally fails with error "Partition with known EFI file not found"
Expected results:
No such errors and the system should be able to get build with Virtual H\W version 17 or 19 in the same way it's getting built with version 15 or below.
Additional info:
NOTE: Whether Secureboot is enabled or not, the behavior remains same [ atlteast for both RHEL 8 and RHEL 9 VMs with HW version 17 and above ]
Redmine: https://projects.theforeman.org/issues/34532
PR: https://github.com/theforeman/foreman/pull/9123
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 (Important: Satellite 6.12 Release), 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:8506