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.
Comment 3Lukáš Hellebrandt
2017-10-19 10:44:12 UTC
Verified with Sat6.3 snap 20.
Reproducer:
1) Follow guide [1] including PXE booting configuration to setup auto provisioning (do not forget to set Domain, Subnet, Content View, Puppet Master, Puppet CA... almost everything, not just required stuff)
2) Create a Client machine in managed subnet (if it's a libvirt machine, don't forget to allow booting from network with maximum priority)
3) Boot the Client, wait for the Discovery OS to do its job
4) In Satellite WebUI, go to Hosts -> Discovered Hosts and click Auto Provision All.
5) Wait for the Client to get provisioned, then ssh login
6) # rpm -q puppet # won't be installed if the bug isn't fixed
7) In Satellite WebUI, check that the system has checked in by looking at the graph in Hosts -> All Hosts -> <Client_host> (the graphs will be empty if the bug isn't fixed)
8) In Satellite WebUI, check that Puppet CA and Puppet Master are set correctly (the fields will be empty if the bug isn't fixed)
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:0336