Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with "Caught TERM; calling stop"

[Jason Antman (JIRA)]

Title: Message Title

Jason Antman commented on an issue   Re: service puppet ensure stopped kills off cron-run puppet with "Caught TERM; calling stop" After some further investigation, it looks like I have a different issue than Jo (the original reporter of this issue). The mcollective puppet agent triggers runs with --daemonize, not with --no-daemonize. Apparently this is done to allow the mcollective process to continue without blocking for the puppet run to complete. So, I suppose, that's really an issue with the mcollective puppet agent, not puppet itself (or, maybe mco needs to run puppet with --pidfile=<some different path>)? Re: the original issue, Jo, running Puppet 3.4.1 on CentOS 6.4 I don't see this problem - if I run "puppet agent --onetime --no-daemonize", /var/run/puppet/agent.pid is not created, and `service puppet status` exits 3 with "puppet is stopped". What version of puppet are you running that exhibits this? Add Comment   Puppet / PUP-1320 service puppet ensure stopped kills off cron-run puppet with "Caught TERM; calling stop" We have recently switched from puppet agent in daemon mode (for kick) to cron-run puppet with mcollective agent. However, I started noticing that puppet policies were being inconsistently applied across the hosts. It turns out that this policy is the problem: <pre> service { 'puppet':         ensure => stopped,         enable => false,   ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.