Issue #3645 has been updated by Alan Barrett. Subject changed from no easy way to push cert signing request rfom client to server to no easy way to push cert signing request from client to server
---------------------------------------- Feature #3645: no easy way to push cert signing request from client to server http://projects.puppetlabs.com/issues/3645 Author: Alan Barrett Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: Branch: It sometimes happens that the puppet client generates a certificate, but then the client is killed before the certificate signing request arrives at the server; or perhaps the request is deleted on the server before being signed. In this state, the client's /etc/puppet/ssl directory does contain a certificate and a signing request: <pre> $ ls /etc/puppet/ssl/* /etc/puppet/ssl/certificate_requests: myclient.example.domain.pem /etc/puppet/ssl/certs: ca.pem /etc/puppet/ssl/private: /etc/puppet/ssl/private_keys: myclient.example.domain.pem /etc/puppet/ssl/public_keys: myclient.example.domain.pem </pre> but "puppetca --list" on the server does not show any pending signing request. No matter how many times I run "puppetd --onetime --test" on the client, it never sends the signing request to the server. It would be nice if, whenever the client detects that its certificate is not yet signed, it sends a signing request to the server, even if it thinks that it had already done so in a previous 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.
