Jira (PUP-5609) Puppet apply doesn't protect shared files with a lock

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on PUP-5609   Re: Puppet apply doesn't protect shared files with a lock I reopened this, because it's been causing problems in CI. Our tests often use puppet apply to manage the puppet service. If the agent is daemonized and is applying a catalog in the background, then calling puppet apply to stop the service will fail with: [root@o3nvm9xl80j4opo ~]# puppet apply -e "service { 'puppet': ensure => stopped }" Notice: Run of Puppet already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists) We could change the tests to specify a unique statedir, most likely via the apply_manifest_on beaker helper, but that is going to take some work. Reopening this until we have a chance to do that (as it affects opensource, PE, and modules pipelines). Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.