Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionCalvin Hartwell
2016-09-02 08:03:09 UTC
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):
6.1.X
6.2.1
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/sat6 server the client running foreman-discovery has connected to while it waits for its kickstart.
Additional info:
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.
VERIFIED
Comment 8Satellite Program
2018-02-21 16:54:17 UTC
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.
>
> https://access.redhat.com/errata/RHSA-2018:0336