On Tuesday, November 6, 2012 2:44:25 PM UTC-8, Forrie wrote:
>
>
> path ~ ^/file_(metadata|content)/files/etc/
> path /file
> auth yes
> allow /^(.+\.)?ourdomain.com$/
> allow_ip 10.0.0.0/8
>
>
This path is still wrong. The path in auth.conf needs to refer to the
LOGICAL path that you set up with the mount point in fileserver.conf, not
to the directory on disk.
In your puppet manifest we see the line:
source => "puppet:///etc/ntp.conf",
This means you must have a mount point called [etc] in fileserver.conf,
right? So regardless of where that mount point points to on disk
(/etc/puppet/files/etc), Puppet knows it as /etc. Therefore, the path in
auth.conf MUST be
path ~ ^/file_(metadata|content)/etc/, NOT /files/etc/ or /files/. You
cannot bulk-control everything in the /etc/puppet/files directory the way
you're trying to, because puppet's fileserver does not know what
/etc/puppet/files is. It knows about each mount point separately, and knows
about them by the name you gave them in fileserver.conf. Put another way,
your auth.conf rules must resemble the puppet:/// URLs you're using to
access the files.
Fix that and you'll fix your problem.
Additionally, it looks like your auth.conf file doesn't have an entry for
node objects yet, which is causing some unrelated errors. You can find out
about that here:
http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-agent-now-requires-node-access
Any word on when a fixed release is going to come out :-)
>
Nope, not yet.
--
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/-/1Y4fV_tcj_EJ.
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.
