[Puppet Users] Odd problem with puppet 3 and module files permissions

Philip Brown
Tue, 18 Dec 2012 16:44:16 -0000

We have an odd situation with a puppet 3 installation. It isnt serving out
the module local files.
We understand (Somewhat) about the new auth.conf requirements, and have
filled those out.
So, access to things such as
puppet:///files/etc/somefile.conf
are working fine.

However, attempts to access
puppet:///modulename/somefile.conf

fail, with
  (in the case of modulename==java)

Error: /Stage[main]/Java/File[/tmp/testfile]: Could not evaluate: Error 400
on SERVER: Not authorized to call find on /file_metadata/java/testfile
Could not retrieve file metadata for puppet:///java/testfile: Error 400 on
SERVER: Not authorized to call find on /file_metadata/java/testfile

Is there some auth.conf setting we''ve missed, that we need to set for
module-local file access?  We already have
path /file
allow *


our fileserver.conf consists of only two sections:

[files]
  path /etc/puppet/files
  allow *.ourdomain.com

[common]
  path /etc/puppet/files/common
  allow *.ourdomain.com


--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit