in simple words, if you want the puppetmaster to be able to send the files to its client, it needs to be able to read the file ;)
Ohad On Fri, Sep 25, 2009 at 7:47 AM, Aldo Foot <luni...@gmail.com> wrote: > > Today I was testing Puppet's fileserver feature and and error came up: > > client> /usr/sbin/puppetd --test --verbose --server puppet > info: Caching catalog at /var/lib/puppet/localconfig.yaml > notice: Starting catalog run > notice: //Node[default]/sudo/Package[sudo]/ensure: created > err: //Node[default]/sudo/File[/etc/sudoers]: Failed to retrieve current > state > of resource: No specified source was found from puppet:///sudo/sudoers > notice: Finished catalog run in 35.44 seconds > > However, inspite of the error, the target sudo rpm would be installed and > /etc/sudoers copied over to the client. > > Initially the permissions on the sudoers file were set to root. > # ls -l /etc/puppet/modules/sudo/files/sudoers > -r--r----- 1 root root 3819 Sep 24 08:56 > > The error went away by changing the permissions to puppet > > # chown puppet.puppet /etc/puppet/modules/sudo/files/sudoers > > Is the entirety of the /etc/puppet directory supposed to be owned by the > puppet user and puppet group? > > ~af > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
