sslamazon-ec2puppetpuppet-enterprise

puppet enterprise ssl cert error


I'm trying to install puppet enterprise on EC2.

The puppet server seems to work fine.

/etc/hosts :

127.0.0.1 puppet

puppet cert list --all : doesn't show anything

On the puppet agent :

/etc/hosts :

10.113.148.136     ip-10-113-148-136.ec2.internal     ip-10-113-148-136      puppet

when I run "puppet agent --test"

Error: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certificate.

On the master:

puppet cert clean bla1.example.com

On the agent:

rm -f /home/ubuntu/.puppet/ssl/certs/bla1.example.com.pem
puppet agent -t

When I run this command on the master. I get the error:

Error: Could not find a serial number for bla1.example.com

And when I run "puppet agent -t" I get the same error message

Also note that in the web-ui: bla1.example.com shows in the "unresponsive" list

When I run "puppet agent --server puppet --waitforcert 30 --test" I get the same error message and afterwards this message:

Info: Retrieving plugin
Error: /File[/home/ubuntu/.puppet/var/lib]: Failed to generate additional resources     using 'eval_generate': SSL_CTX_use_PrivateKey:: key values mismatch
Error: /File[/home/ubuntu/.puppet/var/lib]: Could not evaluate: SSL_CTX_use_PrivateKey::             key values mismatch Could not retrieve file metadata for puppet://puppet/plugins:     SSL_CTX_use_PrivateKey:: key values mismatch
Error: Could not retrieve catalog from remote server: SSL_CTX_use_PrivateKey:: key     values mismatch
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: SSL_CTX_use_PrivateKey:: key values mismatch

Solution

  • In the puppet.conf: server=FQDN does the FQDN in the agents puppet.conf match the private key FQDN in the puppet master in /var/lib/puppet/ssl/private_keys/? I think I ran into a similar issue.