Public bug reported:
Abstract:
When the Puppet agent daemon is unable to get a certificate, it dies on
receiving SIGUSR1.
Longer version:
Right after boot, the Puppet agent daemon is started. It may be running before
hostname resolution is available. If it is, Puppet is unable to receive a
certificate. A Puppet daemon that receives SIGUSR1 should try to do a Puppet
run immediately. But if it has no certificate, it dies instead, leaving the
host unable to receive further configuration until the next reboot.
IMHO, Puppet should not die, but retry fetching a certificate. Barring
that, an upstart job could restart the daemon when it dies. I could
write that upstart job, but I wonder how the maintenance of such
distribution-specific config is organized, and whether to push it
upstream through Ubuntu or through PuppetLabs.
Version data:
Ubuntu Trusty
Puppet 3.4.3-1 0
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397910
Title:
Puppet daemon dies from SIGUSR1 if no certificate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397910/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
