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.

Description of problem:
i have an environment called production that was created during installation of satellite, and when i provision a host in this environment, puppet-agent doesn't
 work and its log says: Did not receive certificate

Version-Release number of selected component (if applicable):
satellite 6.1.8

How reproducible:
always

Steps to Reproduce:
1. provision host
2. wait a few minutes and check systemctl status puppet

Actual results:
Did not receive certificate

Expected results:
puppet should work

Additional info:

additional info is required, mostly logs from provisioned host and foreman-debug.

Moving 6.2 bugs out to sat-backlog.

I just wanted to get a working Satellite 6 environment and provision and control hosts with it, I found this when trying to find out why puppet doesn't work on provisioned hosts. Later we found some workaround and that Satellite instance doesn't exist anymore, so I can't provide more info.

Closing