I upgraded from puppet 0.25.5 to 2.6.12 recently and ended up doing puppetca --clean then --sign again for each of my hosts. Seemed a bit brute force, but it got me out of the bind.
On Fri, Feb 24, 2012 at 12:30 PM, Dan Urist <[email protected]> wrote: > puppet kick ceased working for me when I upgraded to 2.6.3; I've also > tried it with 2.7.10 and get the same result: > >> [email protected] $ puppet kick vanilla.cms.ucar.edu >> Triggering vanilla.cms.ucar.edu >> Host vanilla.cms.ucar.edu failed: Server hostname 'vanilla.cms.ucar.edu' did >> not match server certificate; expected ca >> vanilla.cms.ucar.edu finished with exit code 2 >> Failed: vanilla.cms.ucar.edu > > I've tried using --vardir and --ssldir flags, as suggested by > http://projects.puppetlabs.com/issues/11431, but get the same result. > > Has anyone else seen this? > -- > Dan Urist > [email protected] > 303-497-2459 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
