Description of problem:
We want the foreman-discovery image to report back on which capsule server or satellite server it has connected to. This is so we can use the fact within the discovery rule or kickstart template.
Version-Release number of selected component (if applicable):
Easy to reproduce.
Steps to Reproduce:
1. Load foreman discovery image.
2. Put in capsule/satellite server fqdn and facts.
3. Wait to load...
4. Check foreman for capsule/sat server fact
5. It doesn't exist!
Foreman discovery does not report which capsule/server it has connected to in order to obtain its kickstart
Discovery rules should be able to take into account the capsule/sat6 server the client running foreman-discovery has connected to while it waits for its kickstart.
Upstream bug component is Discovery Plugin
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16420 has been resolved.
Will be part of Satellite 6.3.
Tested with foreman-discovery-image-3.4.1-3.iso.
After registration, there is now a fact in the Software section, discovery_proxy_uri, containing the uri of the server used to discovery the host. Tested both on the Satellite and on a Capsule.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> For information on the advisory, and where to find the updated files, follow the link below.
> If the solution does not work for you, open a new bug report.