Description of problem:

After configuring iPXE and discovery service to complement each other as per https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html-single/provisioning_guide/index#Configuring_Networking-Configuring_gPXE_to_Reduce_Provisioning_Times , even though discovery and build submission is successful via iPXE but the build process is not getting initialized at all, and iPXE is stuck on a Boot Loop as can be seen in the screenshot ipxe-boot-loop.png,

Version-Release number of selected component (if applicable):

Satellite 6.10 [ Latest Snap ]

How reproducible:

Always [ For a VMware VM ]

Steps to Reproduce:
1. Configure satellite\iPXE\Discovery as per https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html-single/provisioning_guide/index#Configuring_Networking-Configuring_gPXE_to_Reduce_Provisioning_Times

2. Ensure that dhcpd.conf has the correct snippet for iPXE

3. Click on "Build PXE Default" in Hosts --> Provisioning Templates page.

4. Create a blank EFI VM in VMware and boot it into the network.

5. When the discovery process completes, create a host from the Discovered host, Ensure to select "iPXE Chain UEFI" as the loader, Submit the build.

6. Monitor the Vmware console for that VM

Actual results:

The discovered VM will get rebooted and then it will boot in the network but It will keep on initiating and fetching ipxe.efi in a continuous loop.

Expected results:

It should initialize the ipxe loader for EFI systems and then fetch vmlinuz and initrd.img to build the system further.

Additional info:

Runtime logs from satellite will be attached later.