Re: [Puppet Users] Puppet works on 41 times out of 43. Help?

On Wednesday, 21 June 2017 19:17:09 UTC+1, Rob Nelson wrote: > > Have you tried to create the link manually to see what happens? > By design, the directory containing the link is owned by root, because we don't want anybody but root to be able create the link. And root can use ln -s -

Re: [Puppet Users] getting a syntax error on the puppet generated code from a forge module (theforeman/foreman_proxy)

On 21/06/17 15:24, Bill Sirinek wrote: I'm trying to set up the foreman_proxy module and getting a syntax error related to resource types. There should be no syntax errors from generated code - unless possibly using old generated code with a bug in the generator, or using generated code

Re: [Puppet Users] getting a syntax error on the puppet generated code from a forge module (theforeman/foreman_proxy)

Here's the file causing the error. I highlighted line 34 of the code, the slash at the end is where the error is pointing. Running puppet parser validate on the file using the 4.10.x agent does not produce this error, but it happens with 4.9.4 (PE 2017.1.1) root@puppetmaster # puppet parser

Re: [Puppet Users] getting a syntax error on the puppet generated code from a forge module (theforeman/foreman_proxy)

On 22/06/17 15:06, Bill Sirinek wrote: Here's the file causing the error. I highlighted line 34 of the code, the slash at the end is where the error is pointing. Running puppet parser validate on the file using the 4.10.x agent does not produce this error, but it happens with 4.9.4 (PE

[Puppet Users] Service set to stopped causes error when the service doesn't exist on Windows

I want to make sure Firefox isn't automatically updating itself on our Windows computers. In most instances, if I have a service set to stopped, not having it installed should equal the same thing. How could I express either is OK in Puppet? service { 'FirefoxUpdateService': name

[Puppet Users] Announce: Puppet Enterprise 2016.4.6 and 2017.2.2 are now available!

Dear Puppet Enterprise Users, Puppet Enterprise 2016.4.6 and 2017.2.2 are now available. These are security and bugfix releases of Puppet Enterprise. All users of Puppet Enterprise 2016.4.x and 2017.2.x are encouraged to upgrade when possible to Puppet Enterprise 2016.4.6 and 2017.2.2,

Re: [Puppet Users] Puppet works on 41 times out of 43. Help?

There might be a bug, but again, you're on an EOL version of puppet. It's entirely possible that any issue you're observing has been fixed already. On Thu, Jun 22, 2017 at 11:56 AM Robert Inder wrote: > On 22 June 2017 at 14:42, jcbollinger

[Puppet Users] getvar and case

Hi, I'm fetching some data in facts using getvar, but as soon as there is a capital letter in the result, the result doesn't go in the variable. For example, this never returns anything: $directive_value_fact = getvar("::zend_directive_fileValue_${name}") The generated fact that I'm

Re: [Puppet Users] getting a syntax error on the puppet generated code from a forge module (theforeman/foreman_proxy)

On 22/06/17 17:14, Henrik Lindberg wrote: On 22/06/17 15:06, Bill Sirinek wrote: Here's the file causing the error. I highlighted line 34 of the code, the slash at the end is where the error is pointing. Running puppet parser validate on the file using the 4.10.x agent does not produce this

Re: [Puppet Users] Puppet works on 41 times out of 43. Help?

On 22 June 2017 at 14:42, jcbollinger wrote: > > > On Thursday, June 22, 2017 at 5:26:41 AM UTC-5, Robert Inder wrote: > > I don't understand why the behavior you describe occurs, but I also don't > understand why you are trying to set the owner of the link in the

Re: [Puppet Users] Puppet works on 41 times out of 43. Help?

On Thursday, June 22, 2017 at 5:26:41 AM UTC-5, Robert Inder wrote: I don't understand why the behavior you describe occurs, but I also don't understand why you are trying to set the owner of the link in the first place, especially if the directory containing it belongs to root. >If I

Re: [Puppet Users] Puppet works on 41 times out of 43. Help?

> On 22 Jun 2017, at 15:42, jcbollinger wrote: > > > So why not go with that? The link owner is relevant only to modifying or > removing the link itself, and since you're managing it via Puppet, I don't > see what purpose it serves to relax the permissions for