The previous certificate was revoked, and the new one was signed. So what you are seeing is true…
On Jan 9, 2012, at 5:11 PM, Gonzalo Servat wrote: > As per the subject, "puppet cert list --all" is showing a heap of revoked > certificates, even though they're not actually revoked. I can go on any of > the revoked clients' host and trigger a Puppet run, and it'll work fine. > > The only reason why they appear revoked is because the systems were > re-installed, so I've issued a puppetca --clean <host> and signed the new > certificate, and it immediately appears as revoked (even though it's not). > > Any ideas? > > Thanks > Gonzalo > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@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. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
