Issue #6026 has been updated by Nigel Kersten. Subject changed from bug in string handler for fileserver.conf in puppet 0.25.5-1 to Config files don't allow for comments at the end of a line anymore Priority changed from High to Low Target version changed from 2.6.x to Statler
To update this, it's not just a fileserver.conf issue. This used to work in 0.24.x, in 0.25.x we broke the ability to have comments at the end of the line. In 2.6.x, our behavior is: <pre> info: mount[files]: allowing *.example.com # no evil access Could not run: Invalid pattern *.example.com # no evil at /etc/puppetlabs/puppet/fileserver.conf:3 </pre> and <pre> err: /File[/var/opt/lib/pe-puppet # vardir/rrd]/ensure: change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /var/opt/lib/pe-puppet # vardir/rrd Could not run: Got 1 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /var/opt/lib/pe-puppet </pre> ---------------------------------------- Bug #6026: Config files don't allow for comments at the end of a line anymore https://projects.puppetlabs.com/issues/6026 Author: f p Status: Accepted Priority: Low Assignee: Category: Target version: Statler Affected Puppet version: 0.25.5 Keywords: fileserver.conf whitespace comments Branch: Hello, using the latest epel package (http://download.fedora.redhat.com/pub/epel/5/x86_64/puppet-0.25.5-1.el5.noarch.rpm) of puppet (centos 5.5) I initially added a comment like so in the fileserver.conf <pre> [mydir] /dir allow 8.8.8.8 # my comment </pre> this causes puppetmasterd to crash without any particular handy warnings as to why in any log files I could discover. I was able to find it with running 'puppetmasterd --no-daemonize --debug --logdest console --verbose' and watching for an error. No big deal on comments not allowed this way, so I removed the "# my comment" leaving a single white space char " " so the entry was "allow 8.8.8.8 " (space after the last 8) and that also causes puppetmasterd to crash without notice. This white space removal seems like a bug to me, but this is by no means critical. Even if the whitespace thing is on purpose the error message should say something rather then have users hunt for this (imo). I searched for any known issues like this but did not find any, so if this is a dupe then I'm blind and sorry for wasting someone's time. keep up the good work puppet developers! -- 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.
