Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/9784 has been resolved.
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