Issue #6884 has been updated by Teyo Tyree.
I believe that I got into this situation by re-provisioning a node without cleaning the certificates on the master. I don't think requesting a fingerprint on the client should require communication with the master. It would be useful for example to be able to compare the fingerprints for a client cert as they exist on the master and on the client. I wonder if we should move this functionality into something like puppet cert --fingerprint on the client. ---------------------------------------- Bug #6884: fingerprint on the client fails if there is a certificate failure on the master https://projects.puppetlabs.com/issues/6884 Author: Teyo Tyree Status: Needs More Information Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: agent, fingerprint Branch: puppet agent --no-daemonize --fingerprint --verbose Could not run: Retrieved certificate does not match private key; please remove certificate from server and regenerate it with the current key Expected behavior is that fingerprint would be returned without attempting to get a catalog. Shouldn't require a puppet run. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
