Bug #16420
closed
Report Smart/Proxy (Capsule) or Satellite server it has connected to
Description
Description of problem:
We want the foreman-discovery image to report back on which proxy server or foreman server it has connected to. This is so we can use the fact within the discovery rule or kickstart template.
How reproducible:
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!
Actual results:
Foreman discovery does not report which capsule/server it has connected to in order to obtain its kickstart
Expected results:
Discovery rules should be able to take into account the capsule/foreman server the client running foreman-discovery has connected to while it waits for its kickstart.
Additional info:
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-discovery-image/pull/79 added
Updated by Lukas Zapletal over 8 years ago
- Subject changed from RFE: Foreman-discovery image does not report back on which Capsule/Satellite server it has connected to to Report Smart/Proxy (Capsule) or Satellite server it has connected to
- Category set to Image
Thanks!
Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-discovery-image|a928c45645837965bf9001d9fc8cdd0e00ca9f43.
Updated by Lukas Zapletal over 8 years ago
QA notes: Each discovered host now contains discovery_proxy_uri and discovery_proxy_facts reported.
Updated by Sachin Ghai over 8 years ago
I can see two new facts under Discovered Host -> 'Software Section':
1) discovery_proxy_type
2) discovery_proxy_uri
discovery_proxy_type proxy
discovery_proxy_uri https://foreman_server:9090