Jira (PUP-9691) Puppet pidlock incorrectly clears lock when running under bundler

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper created an issue   Puppet / PUP-9691 Puppet pidlock incorrectly clears lock when running under bundler Issue Type: Task Assignee: Unassigned Created: 2019/05/03 4:37 PM Priority: Normal Reporter: Josh Cooper When running puppet in bundler, puppet will take ownership of its pidfile even if another puppet process is still running. It's because ps -p <pid> -o comm= returns the entire command line instead of just the process name: $ ps -p 33239 -o comm= /Users/josh/work/puppet/.bundle/ruby/2.5.0/bin/puppet agent --no-daemonize --runinterval 15s --certname wtf18 -v The behavior seems to be ruby or platform specific. On redhat with ruby 2.3: root@k1zm807wxji34df:~# ps -p 17196 -o comm= ruby2.3 root@k1zm807wxji34df:~# ps -p 17196 -o args= ruby2.3 /root/puppet/.bundle/ruby/2.3.0/bin/puppet agent --no-daemonize -v When running puppet from a package, the process name is just puppet [root@dp4uykbg81px49u ~]# ps -p `cat /var/run/puppetlabs/agent.pid` -o comm= puppet This regression was introduced in PUP-9247. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.