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.
Discovery facts are short-lived - they are discarded during provisioning
and they were primarily only meant for discovery rules.
We know it is quite limiting and we were not thinking about pulling
those facts to production stage during the initial design. It turned out
as a useful feature, therefore we are currently changing the way we
store discovered facts and we want to keep them separate from "normal"
facts.
Workaround for Satellite 6.1-6.2 - all facts that start with discovery_
survives the provisioning *until* the initial facter run (which
overwrites everything with it's own set of facts). So you can use these
only during provisioning (e.g. in kickstart template or finish
template). A workaround for this workaround would be to store these
facts on the provisioned system as custom facts, which are then reported
by facter in production mode every 30 minutes. Sounds complicated, but
that's how discovery custom facts work today.