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.

Created attachment 1472647 [details]
screenshot of host

Description of problem: Trying to discover pxebased host failed with 

/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in 'require' : cannot load such file -- facter (LoadError)


Version-Release number of selected component (if applicable):

foreman-discovery-image-3.5.1-2.el7sat.noarch

How reproducible: always


Steps to Reproduce:
1. Try to discover pxe based host using foreman-discovery-image-3.5.1-2.iso or 
2. extract initrd0 and vmlinuz0 from foreman-discovery-image-3.5.1-2.el7sat.noarch (this workaround used because of https://bugzilla.redhat.com/show_bug.cgi?id=1611541)


Actual results: host discovery failed with error
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in 'require' : cannot load such file -- facter (LoadError) (see attachment)


Expected results: successful host discovery


Additional info:

Moving to GA as it was confirmed that this is not present with 3.4.4.

Note: the facter issue may have already been addressed.  If so, please do update the state.

VERIFIED

Version tested:
Satellite 6.4 snap 21

# rpm -qa | grep discovery
foreman-discovery-image-3.5.2-1.el7sat.noarch
tfm-rubygem-foreman_discovery-12.0.2-1.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.4-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-1.0.0-2.el7sat.noarch

No such error on pxe based host discovery.

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/RHBA-2018:2928