Have you tried to create the link manually to see what happens?
Also you probably know but Puppet 3 is EOL. If the issue is with puppet
itself, rather than perms, it's going to require an upgrade to fix.
Unlikely, but wanted to make sure you're aware.
On Wed, Jun 21, 2017 at 1:13 PM Robert Inder
I'm hoping someone can help me diagnose a problem with
Puppet version 3.8.7 running on CentOS 6.4.
I have a couple of servers with a total of 43 web-accessed software
systems, each with its own unix user.
These installations are all created from scratch by Puppet, and then
the appropriate vers
I'm about to update to 2017.2 and start using puppet-job to do runs on
production hosts (we currently only do no-op on production hosts)
Typically when we do a production puppet run, we utilize tags to only run
certain classes. Can we do this when doing puppet runs via the
orchestrator? I c
