Provisioning a RHEL 7 client system stuck at "Booting Kickstart default PXEGrub2" on Red Hat Satellite Capsule 6.18

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.18
  • Red Hat Satellite Capsule 6.18
  • Red Hat Enterprise Linux 7

Issue

  • Provisioning RHEL 7 client systems using PXE/TFTP on UEFI (EFI-based) fails when using Red Hat Satellite Capsule 6.18.

    • During the provisioning process, the client system successfully reaches the GRUB menu but then becomes stuck at the following stage:
     Booting 'Kickstart default PXEGrub2'
    • The system does not proceed further and provisioning does not complete.

Resolution

  • Please refer to the Diagnostic Steps section below to confirm whether your environment matches the symptoms described in this article. If the diagnostics confirm the issue, contact This content is not included.Red Hat Technical Support for further assistance and guidance.

Workaround

Replacing the grubx64.efi file, taken from /var/lib/tftpboot/grub2/, on the Capsule with the same file from an existing working system (RHEL 7 or RHEL 8) allows provisioning to succeed.

  • The workaround could be NOT persistent and may be reverted after running satellite-installer.
  • This issue has been reported to Red Hat Engineering team and is being actively investigated.

Diagnostic Steps

  • On the affected Capsule server, verify the checksum of the grubx64.efi file used for PXE boot.

    1. Run the following command on the Capsule server:

      # sha256sum /var/lib/tftpboot/grub2/grubx64.efi

    2. Compare the output with the expected checksum below:

    # d9e0d5caea5f4a1ace40739aa700d04470fdbaa63085e6b3856e52ae4a551f65
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.