Bug 2170908

Some notes:

A) We can get the discovery successfully completed, by additionally running "satellite-installer --foreman-proxy-http true" on the satellite and opening port 8000 in firewall. 

B) While point A sorts the issue with Discovery itself, Once the host is discovered, I can't create the host from Satellite UI due to this Nasty BUG https://bugzilla.redhat.com/show_bug.cgi?id=2069324#c4 which we haven't fixed ( I don't know why )

C) So I use hammer command and now I can create a host profile from Discovered hosts and Submit it for build i.e.

hammer discovery provision --name mac525400fea371 --hostgroup-id 1 --organization-id 1 --location-id 2 --new-name rhel79 --subnet-id 1 --pxe-loader 'iPXE Embedded' --build true


And that continues to build the host via iPXE approach.

One more thing I discovered as a part of the same testing. 

After enabling the http feature in Comment 1, Everything works fine when the deployment is happening via Satellite.

But When we try to discover the system ( using iPXE ) within a Capsules network, It will fail at the very first Network Boot.


Reason: Capsule's IP is not in the list of trusted_proxies of Satellite\Foreman

Solution: ON satellite add the IP of the capsule ( 192.168.124.3/24 ) as a trusted proxy along with the other localhost entries. 

satellite-installer --foreman-trusted-proxies 127.0.0.1/8 --foreman-trusted-proxies ::1 --foreman-trusted-proxies 192.168.124.3/24

The discovery still fails at some later stage but for now, These much are good enough

(In reply to Sayan Das from comment #2)
> One more thing I discovered as a part of the same testing. 
> 
> After enabling the http feature in Comment 1, Everything works fine when the
> deployment is happening via Satellite.
> 
> But When we try to discover the system ( using iPXE ) within a Capsules
> network, It will fail at the very first Network Boot.
> 
> 
> Reason: Capsule's IP is not in the list of trusted_proxies of
> Satellite\Foreman
> 
> Solution: ON satellite add the IP of the capsule ( 192.168.124.3/24 ) as a
> trusted proxy along with the other localhost entries. 
> 
> satellite-installer --foreman-trusted-proxies 127.0.0.1/8
> --foreman-trusted-proxies ::1 --foreman-trusted-proxies 192.168.124.3/24
> 
> The discovery still fails at some later stage but for now, These much are
> good enough


FYI https://bugzilla.redhat.com/show_bug.cgi?id=2171295

We do not officially support iPXE: https://access.redhat.com/solutions/2674001
I've discussed this with other stakeholders and we don't want to extend support for iPXE.

We do support iPXE only with bootdisk.

@lstejska Does it make sense to use Discovery with bootdisk?

Discovery should not need a bootdisk. We already have something called PXE-Less Discovery which is also an ISO based operation and happens via Discovery + kexec process. 

The sole purpose of this BZ was to confirm whether we will officially support Discovery via iPXE or not and 

If yes, then document the relevant steps
If no, then remove any trace of **Discovery** from iPXE section

Oki, thank you both for clarifying. 
In that case, I'll remove traces of Discovery from iPXE section.

https://github.com/theforeman/foreman-documentation/pull/2833

Published:

- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/provisioning_hosts/index#Configuring_iPXE_to_Reduce_Provisioning_Times_provisioning
- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index#Configuring_iPXE_to_Reduce_Provisioning_Times_provisioning
- https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/provisioning_hosts/index#Configuring_iPXE_to_Reduce_Provisioning_Times_provisioning