Issue #2176 has been updated by Luke Kanies. Keywords set to behaviorchange
---------------------------------------- Bug #2176: Should ignore puppetmasterd.conf and friends http://projects.reductivelabs.com/issues/2176 Author: volcane volcane Status: Closed Priority: Normal Assigned to: Category: Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.8 Keywords: behaviorchange If puppetd.conf, puppetmasterd.conf etc exist the behavior of the various deamons becomes unpredictable. for example, on a machine with just puppet.conf as is current best practice: # puppetmasterd --masterport 5555 --no-daemonize --verbose <snip> notice: Starting Puppet server version 0.24.8 all fine, if however you just touch, or copy puppet.conf to puppetmasterd.conf or even create a valid puppetmasterd config in there it all goes weird, commandline gets ignores, settings reverts to default in some cases etc. This is causing hassle with upgrades since distributions do not delete puppetd.conf, puppetmasterd.conf etc after a upgrade using a package and so post upgrade users find themselves with broken puppet setups that they can't fix since even "puppetmasterd --masterport 5555 --no-daemonize --verbose" just puts the master in the background and doesnt provide any debug info. -- 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 -~----------~----~----~----~------~----~------~--~---
