Description of problem:

 After being deployed via PXE from the Red Hat Satellite server, the provisioned system has everything installed and the first reboot goes correctly as expected because it boots the local HDD. However, any subsequent reboot thereafter results in no boot at all (the HDD seems not to be detected after the PXE timeout), and the system is stuck there.

If manually selecting HDD as first boot device again, the system boots as expected.

The customer wants to maintain the boot order as 1) PXE and 2) HDD so that if they need to redeploy the system, it's enough to instruct Satellite to deploy that system via PXE and give a reboot to the machine, etc.

How reproducible:

Always

Is this issue a regression from an earlier version:

No.

Steps to Reproduce:

PXE provisioning of a system via Red Hat Satellite server.

Actual behavior:
Please refer to the problem description section above.

The first reboot of the provisioned system goes correctly as expected because it boots the local HDD. However, any subsequent reboot thereafter results in no boot at all (the HDD seems not to be detected after the PXE timeout), and the system is stuck there.

Expected behavior:
Subsequent reboots after the first reboot of the system being provisioned get successfully completed even with the boot order maintained as 1) PXE and 2) HDD in the BIOS/EFI.

Business Impact / Additional info:

When the customer wants to redeploy the system, they have to manually modify the boot order in BIOS/EFI to be 1) HDD and 2) PXE.

QE Tracker for https://issues.redhat.com/browse/SAT-33455