|
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).
|