Description of problem: This is a heads-up related to 2 Grub2 BZs: - BZ #2032294 - BZ #2048904 When network booting a system, there is grub.cfg file used to chainload to local disk upon system installation. The template needs to be updated to make sure software raid systems and/or VMWare systems can chainload successfully. The solution consists in: - calling a new "connectefi scsi" command prior to searching for local disk boot loader (e.g. "search --file ... /EFI/BOOT/BOOTX64.EFI") - modifying "search --file" commmand to restrict to EFI disks ("search --file --efidisk-only ... /EFI/BOOT/BOOTX64.EFI") Version-Release number of selected component (if applicable): All satellite releases
Thanks for this, we already saw some complaints about this. That is an easy change, let me do this right away!
Thank you very much, we temporarily disabled chainbooting because I could not figure this out, but let's put it back: https://github.com/theforeman/foreman/pull/9175
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34702 has been resolved.
Verified. Tested on Satellite 6.12.0 Snap 5.0 Steps followed: 1. Go to Host > Provisioning Templates 2. Search for `pxegrub2_chainload` template Observation: The template is updated with the warning message: ``` echo "VMWare hosts with QuickBoot feature enabled may not find the local ESP" echo "partition due to not initializing all the EFI devices. To workaround, upgrade" echo "to the latest grub2 (*) and uncomment "connectefi scsi" statement in the" echo "grub2_chainload template." echo echo "Virtual or physical hosts using Software RAID for the ESP partition may try" echo "booting on the Software RAID, which will fail. To workaround, upgrade to the" echo "latest grub2 (*) and add "--efidisk-only" argument to the "search" command in" echo "the grub2_chainload template." echo echo "(*) grub2-efi-x64-2.02-122.el8 (upstream doesn't have the patches yet)" echo #connectefi scsi ```
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