Dumb question, but have you verified the new certificate is in place on the Foreman web interface?
1. On one test host stop puppet, wipe out the all of the SSL certificates, 2. clean out the host on the Puppet Server using "puppet cert clean" 3. Run puppet agent -tv on the host 4. Re-sign the client certificate with Puppet and then see if the SSL self-signed certificate issue goes away. While I don't have hands on a server/client to test, I remember having this sort of problem hit me with a CA signed Cert expired. The puppet client to host certs were fine, but when it tried to send the reports to Foreman there was a cert issue that caused problems. I don't guarantee this will provide any help, but it may be a start. Also you could run the puppet agent in full debug mode (--debug) to see if there is anything there that complains about the certificate. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
