An update on what I'm seeing:
the file_metadata request is going to correct puppet master. The
file_content request is going to the master that compiled the manifest.
Fails because the master that compiled the config does not have a copy of
the files -- and it should have to if the file resource is telling it
explicitly which server to get it from.
Bug?
On Tuesday, March 18, 2014 12:22:42 PM UTC-4, Roger wrote:
>
> I'm trying to get an agent to pull files from a separate master acting as
> a file server. No filtering on permissions based on IP or fqdn, standard:
>
> path /file
> allow *
>
> in auth.conf
>
> mount point in fileserver.conf with allow *
> ie.
> [myfiles]
> path: /opt/myfiles
> allow *
>
> File resource is:
>
> file {'name':
> source => 'puppet://puppet.master.one/myfiles/file'
> }
>
> Have 2 identical puppet masters. Both running 3.3.2. Also tried with a
> separate 3.4.3 master.
>
> If I use puppet agent --server puppet.master.one then all works fine. If
> I use puppet agent --server puppet.master.two, file_metadata works fine,
> sees changes made to the file on puppet.master.one but file_content always
> fails with permission denied.
>
> Have tried every possible combination of permissions in auth.conf of
>
> path /file_content/
> allow *
>
> path /file_metadata/
> allow *
>
> All before the default "path /file" line. Pull them out, put them in,
> rearrange, mix in a blender......nothing works.
>
> Am I missing something? Has anyone gotten puppet to pull files from
> separate master?
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/498850a0-7ce3-4f15-b45c-d73fd2b8cd5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
