Puppet users - Dec 2012 - Odd problem with puppet 3 and module files permissions

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
https://groups.google.com/d/msg/puppet-users/-/8AHUcL3-aZQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tuesday, December 18, 2012 8:51:25 AM UTC-8, Branan Purvine-Riley
wrote:
>
>
>
> In Puppet 3, you must explicitly state that the file you are requesting is 
> from a module. Try:
> puppet:///modules/${modulename}/somefile.conf
>

D''oh... I guessed it was something like that, but I used /module/
instead
of /modules/  :-D

works now, thanks.

Would be nice if
http://docs.puppetlabs.com/puppet/3/reference/release_notes.html

was updated with a Really Big Notice (ie: with its own section entry) about 
how now you need to do this.


 

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/uyC6EERESg4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.