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

Branan Purvine-Riley
Tue, 18 Dec 2012 16:51:25 -0000

On Tue, Dec 18, 2012 at 8:44 AM, Philip Brown <phil@bolthole.com> wrote:

> 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
>
>

In Puppet 3, you must explicitly state that the file you are requesting is
from a module. Try:
puppet:///modules/${modulename}/somefile.conf