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!
> 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.
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.
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