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.
Steps to Reproduce:
1) Create Vm Machine in vmware with Red hat 6 or 7.
2) Then register and subscribe the vm to Satellite
3) Download the packages, puppet
4) populate the /etc/puppet.conf
Other Details and
certificate_revocation = false
5) Run puppet agent -t -o
6) Sign the certificate with (because we have no autosign)
puppet cert sign --all
7) Then run puppet-agent -t -o ( we have to run puppet agent again to get environment)
Getting error:
Exiting; no certificate found and waitforcert is disabled
We found workaround, but this requires extra steps,
########################################
1) Create Vm Machine in vmware with Red hat 6 or 7.
2) Then register and subscribe the vm to Satellite
3) Download the packages, puppet
4) populate the /etc/puppet.conf
Other Details and
certificate_revocation = false
5) Run puppet agent -t -o
6) Sign the certificate with (because we have no autosign)
puppet cert sign --all
7) From Satellite Master, run :
puppet cert clean hostname,
8) from puppet agent(host)
rm -rf /var/lib/puppet/ssl/*
9) Then run puppet-agent -t -o ( we have to run puppet agent again to get environment)
10) Go to Satellite and assign the puppet environment
11) it now works
How can we get this working without the extra steps?
this can be closed, issue was resolved by:
The issue was resolved by signing the certificate before puppet agent was run.
This was resolved by running adding a timer to puppet with -w option.
We also added certificate_revocation = false however not confirmed if this fix helped the issue.
In addition to that, the order of enabling and puppet was changed.