Yes, the puppet server was running as user "puppet", but that hint helped
me recollect an old issue we had, which eventually helped me resolve this
symlink to NFS share issue.
A few months ago, we started using extended groups option on our NetApp
(cluster mode). With this option enabled, local
The Puppet *server* should be running as 'puppet' or 'pe-puppet', not
'root'.
Can you double check that this isn't the root of your issue?
Trevor
On Tue, Jan 3, 2017 at 2:10 PM, PK wrote:
> Rob,
>
> No. Symlink to a local file system works fine.
>
> Tried it with:
> dev -> /tmp/dev
> dev2 -> /
Rob,
No. Symlink to a local file system works fine.
Tried it with:
dev -> /tmp/dev
dev2 -> /etc/puppetlabs/code/environments/devorig
Trevor,
SELinux is disabled and the puppet master server has full superuser access
to the NetApp volume/directory. The client cannot see those NFS directories
Do you have SELinux enabled?
Also, do you have 'all_squash' enabled on your NFS directories?
Trevor
On Mon, Jan 2, 2017 at 5:51 PM, PK wrote:
> Hi All,
>
> I seem to be running into an issue when I try to use environments in my
> test Puppet 4 setup. I am in the process of migrating from Puppe
Does this happen if you use a symlink to a local file system location? dev
-> /tmp/dev for example?
On Tue, Jan 3, 2017 at 4:32 AM PK wrote:
> Hi All,
>
> I seem to be running into an issue when I try to use
>
> environments in my test Puppet 4 setup. I am in the process of migrating
>
> from Pu
Hi All,
I seem to be running into an issue when I try to use environments in my
test Puppet 4 setup. I am in the process of migrating from Puppet 3 to
Puppet 4.
puppetserver version: 2.7.2
puppet agent: 4.8.1
Server is running CentOS Linux release 7.3.1611
If I create local directories
/etc/p
