On Thu, Jan 6, 2011 at 08:29, Adam Heinz <a...@metricwise.net> wrote:
> I get that message when I rebuild a server in place. Puppetmaster is
> complaining that the public key it expects for your node has changed.
> On your puppetmaster as root, do:
>
> find /var/lib/puppet/ssl/ -name $1.pem -delete
> sed '/$1/d' /var/lib/puppet/ssl/ca/inventory.txt > /tmp/inventory.txt
> mv -f /tmp/inventory.txt /var/lib/puppet/ssl/ca/inventory.txt
>
> where $1 is the fqdn of the node.
A better way to do this is to use the Puppet CA application:
] puppet cert --clean $1 # $1 is the node name, as before
(on older releases, puppetca --clean)
That does pretty much the same thing, but does the right locking and
everything else. Plus, if you suddenly need to start doing something
more on the node puppet labs will update that application to do it,
while the DIY version means you need to know what goes on inside our
CA. :)
Regards,
Daniel
--
✉ Daniel Pittman <dan...@rimspace.net>
⌨ dan...@rimspace.net (XMPP)
☎ +1 503 893 2285
♻ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
