Document URL:

https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index?lb_target=preview#

Section Number and Name:

Chapter 5. Configuring iPXE to Reduce Provisioning Times

4th point in last Procedure section , just above "5.1. Booting Virtual Machines"

Describe the issue:

We mention this:

~~
Optionally, configure Foreman discovery. For more information, see Chapter 7, Configuring the Discovery Service.

• In the Satellite web UI, navigate to Administer > Settings, and click the Provisioning tab.

• Locate the Default PXE global template entry row and in the Value column, change the value to discovery.
  ~~

That link takes us to https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index?lb_target=preview#Configuring_the_Discovery_Service_provisioning and in has no relevant details about iPXE with Discovery at all.

Let's say we have completed the other prerequisites and also tested the "5.1. Booting Virtual Machines" successfully, The Discovery via iPXE itself will fail when attempting and selecting the Discovery option from iPXE global menu.

as port 8000 has no services running but iPXE\Httpboot will try to use that with httpboot endpoint to fetch fdi-image vmlinuz file.

Suggestions for improvement:

• First, Please decide if we will be fully supporting the Foreman DIscovery over iPXE for BIOS-based systems.

• If yes, Then we need to ensure that we have proper steps documented about it.

Additional information:

Consider fixing 6.12 and 6.11 as well