Description of problem: "puppet-agent" is available in the rhel-7-server-satellite-tools-6.7-rpms repo and contains everything needed to register host to Satellite 6.7 manually but the regular "puppet" package is not present in the repo (seems it was moved to rh-common repo). When using the bootstrap.py script to register hosts to Satellite 6.7 it will try to yum install puppet and fail because the package does not exist in any repos ( assuming you only have Base + Satellite-Tools-6.7 ).
brenden, the puppet-agent package in sat-tools has a "provides: puppet", so it should actually work.
Evgeni, you're right that the puppet-agent package provides puppet but it seems that bootstrap.py explicitly tries to run "yum install puppet" and fails. Shouldn't the bootstrap.py script instead be running "yum install puppet-agent" at that step? I was on a customer site and could not get logs or example output but I will see if I can reproduce this on another Satellite 6.7 to confirm
(In reply to Brenden Wood from comment #4) > Evgeni, you're right that the puppet-agent package provides puppet but it > seems that bootstrap.py explicitly tries to run "yum install puppet" and > fails. Shouldn't the bootstrap.py script instead be running "yum install > puppet-agent" at that step? Yeah, it *should*. And that's also what I've implemented in the PR (https://github.com/Katello/katello-client-bootstrap/pull/328) as nothing uses the old "puppet" name anymore. However, yum should just fine resolve that provides and install the "puppet-agent" RPM when it is asked to install "puppet" > I was on a customer site and could not get logs or example output but I will > see if I can reproduce this on another Satellite 6.7 to confirm That'd be cool. We'll fix/cleanup the code either way, but would be good to know how quickly we need to push the fix out.
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 (Important: Satellite 6.8 release), 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-2020:4366