Issue #1855 has been updated by luke. Status changed from Unreviewed to Accepted Priority changed from Normal to High
Can someone reproduce this? It's certainly dangerous, and I can't imagine how it's happening. ---------------------------------------- Bug #1855: puppetd --noop doesn't take effect in the presence of old puppetd.conf file... http://projects.reductivelabs.com/issues/show/1855 Author: ant Status: Accepted Priority: High Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.6 Keywords: When running puppetd --noop with a deprecated puppetd.conf in /etc/puppet the noop has no effect, leading to potentially catastrophic changes in what should be safe pre-production testing run... This setup could occur (and did occur in my environment) after an rpm upgrade from an older pre-single-config-file version of puppet. To reproduce: * copy puppet.conf to puppetd.conf * change the section header [main] to [puppet] in puppetd.conf * run puppetd --test --noop * notice that the noop doesn't work... * delete the puppetd.conf and re-run * notice that the noop works again ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
