Jurjen Bokma j.bo...@rug.nl writes:
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.
The init scripts, upstart jobs, systemd services, and whatever someone
will think of next to start a service, is handled by the distribution
packaging. The puppet packages in Ubuntu trusty, utopic and vivid are
unmodified from the ones in Debian.
I will gladly add upstart jobs for the various puppet services to the
Debian packaging. If you would like to contribute some of them, please
attach them to this Launchpad bug, or to a Debian BTS bug.
Using respawn does sounds like a workaround in this case, though. I'd
say that puppet agent dying on SIGUSR1 in some phase of startup is a
bug.
I did a few searches at the upstream bug tracker
(https://tickets.puppetlabs.com/browse/PUP), but could not find any bug
filed for it, open or closed.
--
Stig Sandbeck Mathisen
--
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