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

[Philipp Gassmann (JIRA)]

Title: Message Title

Philipp Gassmann commented on PUP-5609   Re: Puppet apply doesn't protect shared files with a lock the apply process should check and set the same lock files as the agent. With --statedir /tmp/foo it should be possible to run it anyways. We now use the following workaround with hardcoded paths: mkdir -p $environment # Puppet 4 requires an environment directory # check puppet agent disable lock file [ -f /opt/puppetlabs/puppet/cache/state/agent_disabled.lock ] && ( echo 'Puppet agent disabled - skipping' >&2; cat /opt/puppetlabs/puppet/cache/state/agent_disabled.lock >&2; echo >&2; exit 1 ) # check and set lockfile for puppet apply ( flock -n 9 || ( echo 'Puppet agent lock file exist - skipping' >&2; exit 1 ) puppet apply \ --test \ --show_diff \ --write-catalog-summary \ --modulepath=modules:site \ --hiera_config=hiera.yaml \ --environmentpath=. \ --environment $environment \ manifests/site.pp "$@" ) 9>/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock 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.