Issue #5455 has been updated by Peter Meier.
or as a workaround you can start `--test` with an additional option `--pidfile /tmp/test.puppet` which will allow you to run puppet as the locking mechanism is quite dumb and is just looking for the pidfile. Afair there is already a ticket from Volcane regarding that issue. ---------------------------------------- Feature #5455: puppetd --noop --test should work when puppetd --disable https://projects.puppetlabs.com/issues/5455 Author: micah - Status: Unreviewed Priority: Low Assignee: Category: agent Target version: Affected Puppet version: Keywords: Branch: If you disable puppet from running by issuing: <pre> # puppetd --disable </pre> and then you want to see what will be changed when you enable puppet again, you cannot do this: <pre> # puppetd --test --noop notice: Run of Puppet configuration client already in progress; skipping </pre> You have to enable puppet again before you can run the noop: <pre> # puppetd --enable # puppetd --test --noop </pre> Its a minor annoyance, but it seems like that is an unnecessary restriction, especially since you are likely to re-disable it again immediately after a noop run. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
