Issue #4227 has been updated by Luke Kanies.
For the record, this is theoretically a feature (and should be in the ticket db somewhere). People used to complain that puppetd would die if puppet.conf was borked, which made it very hard to fix it. It should at least be logging the failure, but at least puppetd should always be resilient to invalid config files. ---------------------------------------- Bug #4227: puppet executables ignore puppet.conf if it is borked https://projects.puppetlabs.com/issues/4227 Author: Dan Bode Status: Accepted Priority: Normal Assignee: Category: Target version: queued Affected Puppet version: 0.25.5 Keywords: Branch: this is not a new issue, I find it highly annoying though. 1. working config <pre> [puppet] modulepath=/your/mom/ </pre> <pre> # puppet --configprint modulepath /your/mom/ </pre> now bork it <pre> [puppet] modulepath=/your/mom/ BORKED </pre> <pre> # puppet --configprint modulepath /etc/puppet/modules:/usr/share/puppet/modules </pre>h puppet silently ignores the entire puppet.conf file and uses the defaults for all options... how annoying. -- 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.
