Sometimes, we spin up a new node by using a cert name previously known to the Puppet Master, especially in immutable infrastructures. Our Puppet infrastructure is designed with certificate security in mind, so having a new node with a name already known by the Puppet Master will present a message like the following:
[root@wordpress puppet]# puppet agent -tError: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. Did you forget to run as root?Certificate fingerprint: 88:7F:B2:88:15:20:0A:55:3F:DE:2A:36:2C:B1:52:50:F1:77:96:EA:79:75:A1:00:B9:D6:3E:0B:93:45:D8:1CTo fix this, remove the certificate from both the master and the agent and then start a puppet run, which ...
