Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-41385

RHEL 7 PXE/TFTP Provisioning on EFI Fails After Upgrading Satellite from 6.17 to 6.18

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 6.18.0, 6.18.1
    • Provisioning
    • False
    • sat-rocket
    • None
    • None
    • None
    • Automated

      Description of problem:

      After upgrading Red Hat Satellite from version 6.17 to 6.18, issues are observed with RHEL 7 provisioning.

      Provisioning new RHEL 7 systems via PXE/TFTP on EFI-based systems no longer works. The system becomes stuck on the “Booting 'Kickstart default PXEGrub2'” screen immediately after the GRUB menu.

       

      Is this issue a regression from an earlier version:

      Yes.

      • The issue starts occurring after upgrading Satellite to version 6.18.
      • On Satellite 6.17, RHEL 7 provisioning using the same method works without any issues.

      Steps to Reproduce:

      • Upgrade Satellite and Capsule from version 6.17 to 6.18.
      • Attempt to provision a RHEL 7 client system using PXE/TFTP on an EFI-based machine.

      Actual behavior:

      • RHEL 7 provisioning fails after upgrading Satellite to 6.18.
      • During PXE boot on EFI systems, the machine hangs at the “Booting 'Kickstart default PXEGrub2'” screen after the GRUB menu.
      • Provisioning does not proceed beyond this point.

       

      Workaround:

      Replacing the grubx64.efi file on the Capsule at:

      ~~~

      /var/lib/tftpboot/grub2/

      ~~~

      • with the same file from an existing working system (RHEL 7 or RHEL 8) allows provisioning to succeed.
      • However, this workaround is not persistent and may be reverted after running satellite-installer.

       

      Expected behavior:

      RHEL 7 provisioning via PXE/TFTP on EFI systems should complete successfully after upgrading Satellite to version 6.18.

       

      Business Impact / Additional info:{}

      • The issue is encountered during testing in a development environment prior to performing the upgrade in production.
      • This regression may block or delay production upgrades for environments that still require RHEL 7 provisioning.

       

              Unassigned Unassigned
              rhn-support-mkushwah Mohit Kushwah
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: