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.
Bug 1598080 - Provide rubygem-facter package in Server and Capsule repos
Summary: Provide rubygem-facter package in Server and Capsule repos
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.4.0
Assignee: satellite6-bugs
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks: 1598020
TreeView+ depends on / blocked
 
Reported: 2018-07-04 10:00 UTC by Lukas Zapletal
Modified: 2019-11-05 23:27 UTC (History)
3 users (show)

Fixed In Version: foreman-discovery-image-3.5.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 18:57:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lukas Zapletal 2018-07-04 10:00:46 UTC 
Hello!

We ship two facters:

puppet-agent = facter 3.x
tfm-rubygem-facter = facter 2.x

Foreman discover image relies on Facter 2.x and previously the package named "facter" was actually provided by rubygem-facter. This changed and it is now facter3 (puppet-agent) which breaks FDI completely - it does not boot up.

Please add non-SCL version (rubygem-facter) back into repos, we will change dependency from "facter" to "rubygem-facter" so build for Satellite 6.4 can be created. Ticket to refactor to puppet3 has been filed.

https://projects.theforeman.org/issues/24153
https://projects.theforeman.org/issues/24154

This is BLOCKER issue for FDI 3.5.0. We most likely want to allow users to install one or another for their clients which is benefit of shipping the package (they'd need to instal TFM ruby today).

This blocks FDI ALHPA build, setting higher severity. Thanks!
Comment 2 Ewoud Kohl van Wijngaarden 2018-07-04 10:16:00 UTC 
> puppet-agent = facter 3.x
> tfm-rubygem-facter = facter 2.x

Facter always has ruby bindings, both facter 2 and facter 3. It's just that puppet-agent bundles its own ruby and installs the bindings for *that* ruby. tfm-rubygem-facter installs bindings for the tfm Ruby version. FDI uses the system ruby so the bindings are not available. In upstream we depend on a facter (without any prefix) from EPEL that installs its bindings in the system ruby.

In this case puppet-agent provides facter because it does install /opt/puppetlabs/bin/facter and is added to $PATH so it's sort of correct in the provides. Ideally the system facter would Provide: rubygem(facter) and we could depend on that but the one in EPEL/Fedora doesn't provide that either so it's not really a fix we can universally apply now.

Short term we should include an equivalent facter package as EPEL builds it. Longer term I think we should get that rubygem(facter) provides in.
Comment 12 Nikhil Kathole 2018-10-01 10:57:55 UTC 
VERIFIED

Version tested:
Satellite 6.4 snap 24

Discovery is working with tfm-rubygem-facter-2.4.0-5.el7sat.x86_64 and foreman-discovery-image-3.5.3-1.el7sat.noarch.
Comment 13 Bryan Kearney 2018-10-16 18:57:36 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:2927
Note You need to log in before you can comment on or make changes to this bug.