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
Hi,
OK trying to evaluate how much work and effort it's going to be to move to
Puppet v4.x I have switched on the future parser in our Dev environment.
I am now getting this kind of thing:-
$ puppet agent -t --trace
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error:
- Original Message -
> From: "Paul Seymour"
> To: "puppet-users"
> Sent: Tuesday, 3 January, 2017 11:57:02
> Subject: [Puppet Users] Trouble with future parser ?
> Hi,
>
> OK trying to evaluate how much work and effort it's going to be to move to
> Puppet v4.x I have switched on the f
On Tuesday, 3 January 2017 10:59:42 UTC, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Paul Seymour" >
> > To: "puppet-users" >
> > Sent: Tuesday, 3 January, 2017 11:57:02
> > Subject: [Puppet Users] Trouble with future parser ?
>
> > Hi,
> >
> > OK trying to evaluate
- Original Message -
> From: "Paul Seymour"
> To: "puppet-users"
> Sent: Tuesday, 3 January, 2017 12:05:45
> Subject: Re: [Puppet Users] Trouble with future parser ?
> On Tuesday, 3 January 2017 10:59:42 UTC, R.I. Pienaar wrote:
>>
>>
>>
>> - Original Message -
>> > From: "Paul
On Tuesday, 3 January 2017 11:07:53 UTC, R.I. Pienaar wrote:
>
>
>
>
> yes, so this class needs access to the variable in question, best to pass
> it
> into it as a property
>
Yeah got it thanks. What I missed looks way more obvious when I lay it out
in a mail. Not fully back after the holid
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 everybody,
example42 wishes a happy and healthy new year to everybody.
We are happy to announce that we have a Puppet job opening:
Intermediate or Senior Puppet DevOps Consultant - Berlin, Germany, Europe, Earth
Example 42 GmbH is looking for an Intermediate or Senior DevOps/Puppet
Consultan
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
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
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 -> /
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
Rob, is there a way to set 'stringify_facts = false' globally on the puppet
server or this must be done on all clients? I just hit this with a
puppetlabs module and setting to false on the agent worked. Obviously I
would rather set t once on the server.
Thanks
On Sunday, November 6, 2016 at 10
13 matches
Mail list logo
