Currently, if one sets START=no in /etc/default/puppetmaster, the init script will
exit with exit-code 0, regardless of whether the service is running or not. In the
case where you have a puppet manifest like:
service { 'puppetmaster': ensure => stopped }
Puppet will try to stop the service on every agent run, because status is returning
zero, so Puppet thinks it is running.
Currently, if one sets START=no in /etc/default/ puppetmaster, the init script will
exit with exit-code 0, regardless of whether the service is running or not. In the
case where you have a puppet manifest like:
service { 'puppetmaster': ensure => stopped }
Puppet will try to stop the service on every agent run, because status is returning
zero, so Puppet thinks it is running.
This issue was fixed upstream in this commit:
https:/ /github. com/puppetlabs/ puppet/ commit/ e48902a7d881e84 861d366af5ff88f c0146037da
As it's a one-liner, could this be backported into the Debian packages?
Thanks,
Greg
-- System Information:
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Architecture: amd64 (x86_64)
puppetmaster: nova.clouds. archive. ubuntu. com/ubuntu/ precise- updates/ main amd64 Packages
Installed: 2.7.11-1ubuntu2.7
Candidate: 2.7.11-1ubuntu2.7
Version table:
*** 2.7.11-1ubuntu2.7 0
500 http://