Wednesday, December 17, 2014

The certificate retrieved from the master does not match the agent's private key.

While implementing puppet in our environment, I got into this issue with newly created machine. Running 'puppet agent -t' for the first time:

First you must make sure the certname in puppet.conf matches the hostname of the machine, but the commands mentioned above may still not work and result in the same error.

After a little digging on the puppet master machine, I found the following domain.com.pem file in the following path:
/var/lib/puppet/ssl/ca/signed
Just remove this agent's pem file, and redo the commands again. Fixed the issue for me.

Edit: Also ensure you are working under root in puppet master :P

1 comment:

  1. The RNG or Random Number Generator makes use of hundreds of thousands of coding that make 1xbet it work like a safe combination lock. To trigger wins, these are randomly unlocked without any influence. The RTP or Return to Player algorithm is based on the theoretic of a million spins, so winning and winning big is all about luck.

    ReplyDelete

Ansible and Jinja2: Check if variable is defined and it's True

Jinja2 provides you with a built in test: http://jinja.pocoo.org/docs/2.10/templates/#defined So you can simply use: However, if you...