#1190: Puppetd exits if it receives a bad certificate
-------------------+--------------------------------------------------------
Reporter: init | Owner: community
Type: defect | Status: new
Priority: normal | Component: client
Version: 0.24.4 | Severity: normal
Keywords: | Stage: Unreviewed
Patch: None | Complexity: Unknown
-------------------+--------------------------------------------------------
When starting puppetd in daemon mode, a bad certificate received from the
puppet master causes the client to exit. This is (according to me)
undesirable behavior. Why not just retry once in a while like when there
is no signed client certificate on the master for this host? As of now, if
the client is reinstalled without first removing the old puppet client
certificate, the system administrator must then manually login to the
client to restart the puppet daemon (after removing the old certificate).
In my opinion, a daemon should not exit unless in encounters a truly fatal
error, and this error is not one of them. An example of a truly fatal
error would be a missing dependency.
Unfortunately, I do not know Ruby (yet), so I cannot fix it.
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1190>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
