[Puppet Users] Bug: Exec resource executes although dependencies have failed

2014-12-16 Thread Dirk Heinrichs
Hi, on Puppet 3.7.3 (Windows) I currently see the following strange behaviour: Notice: /Stage[main]/Myclass/Exec[myexec]: Dependency Exec[myotherexec] has failures: true Warning: /Stage[main]/Myclass/Exec[myexec]: Skipping because of failed dependencies Debug: Exec[myexec](provider=windows): Exec

Re: [Puppet Users] Bug: Exec resource executes although dependencies have failed

2014-12-16 Thread Felix Frank
On 12/16/2014 10:11 AM, Dirk Heinrichs wrote: > Hi, > > on Puppet 3.7.3 (Windows) I currently see the following strange behaviour: > > Notice: /Stage[main]/Myclass/Exec[myexec]: Dependency Exec[myotherexec] > has failures: true > Warning: /Stage[main]/Myclass/Exec[myexec]: Skipping because of fai

[Puppet Users] Class ordering via anchor patterns not working in a pretty simple setup

2014-12-16 Thread Abhijeet Rastogi
Hi everyone, I've 2 simple base classes: class profile::base { anchor { 'base_repos_start': } class { '::yum::repo::epel': require => Anchor['base_repos_start']} class { '::yum::repo::puppet': require => Anchor['base_repos_start']} anchor { 'base_repos_end': } } class profile::opensta

[Puppet Users] Re: future parser, defined types, and variable scope

2014-12-16 Thread jcbollinger
On Monday, December 15, 2014 11:07:45 AM UTC-6, John Sellens wrote: > > I couldn't find any reference to this different behaviour, so I'm > wondering if anyone knows if this is intentional. > > I use a bunch of defined types, and with the future parser, when I refer > to a variable in a templa

Re: [Puppet Users] future parser, defined types, and variable scope

2014-12-16 Thread Erik Dalén
On Mon Dec 15 2014 at 6:07:43 PM John Sellens wrote: > I couldn't find any reference to this different behaviour, so I'm > wondering if anyone knows if this is intentional. > > I use a bunch of defined types, and with the future parser, when I refer > to a variable in a template, it seems that th

Re: [Puppet Users] puppet agent restarting everyday?

2014-12-16 Thread Suresh P
Hi, This is configured to run daily by puppet installation itself. Does this restart puppet agent? /var/log/puppet/*log { missingok notifempty create 0644 puppet puppet sharedscripts postrotate pkill -USR2 -u puppet -f 'puppet master' || true [ -e /etc/init.d/puppet ] && /etc/i

[Puppet Users] Hiera has stopped working correctly!

2014-12-16 Thread Guy Matz
Hiera is not honoring my hierarchy :-( gmatz@bunnybear ~/Code/puppet $ cat hiera.yaml --- :hierarchy: *- "%{::environment}"* - common :backends: - eyaml - yaml :merge_behavior: deeper :eyaml: :datadir: /home/gmatz/Code/puppet/hieradata :pkcs7_private_key: /home/gmatz/Code/puppet/keys/p

Re: [Puppet Users] puppet agent restarting everyday?

2014-12-16 Thread Dirk Heinrichs
Am 16.12.2014 um 15:26 schrieb Suresh P: > This is configured to run daily by puppet installation itself. Does > this restart puppet agent? > > /var/log/puppet/*log { > missingok > notifempty > create 0644 puppet puppet > sharedscripts > postrotate > pkill -USR2 -u puppet -f 'puppet

[Puppet Users] Re: Hiera has stopped working correctly!

2014-12-16 Thread Gavin Williams
Guy I think you need to pass in your environment to hiera using '::environment' rather than 'environment', as your hiera.yaml is looking for '::environment'... Similar issue/resolution here: https://ask.puppetlabs.com/question/3635/how-do-i-specify-environment-to-hiera-on-the-command-line/?an

Re: [Puppet Users] Reading configuration from UI.

2014-12-16 Thread jcbollinger
On Monday, December 15, 2014 4:54:04 AM UTC-6, glos...@gmail.com wrote: > > Hi Felix, > > I have not quite got your reply. > > This configuration values will apply to the service managed by the puppet > infrastructure. > > What i meant is whether there is any support from puppet to read config

Re: [Puppet Users] puppet agent upgrade on windows

2014-12-16 Thread Jason Chinsen
Thanks Rob! On Monday, December 15, 2014 11:21:52 AM UTC-5, Rob Reynolds wrote: > > > > On Mon, Dec 8, 2014 at 8:27 AM, Jason Chinsen > wrote: >> >> Hello Rob >> >> Thanks for the response. I will take a look at OpenTable's module for >> sure. I will also add -force on to my install line >> >> F

[Puppet Users] Re: trouble getting list of nodes via PE 3.7 Rest API

2014-12-16 Thread Byron Miller
Looks like you're using puppetDB api to query your puppet master? try just puppetmaster:443/{environment}/nodes - environment being "production" or whatever the default env is. or if querying puppetdb try /v3 api endpoint instead of /v1 On Monday, December 15, 2014 11:41:17 PM UTC-6, red wrot

[Puppet Users] Installing a specific OL6 Kernel version...

2014-12-16 Thread Gavin Williams
Afternoon all A requirement has arisen for using Puppet to install a specific version of the kernel package on our Oracle Linux 6 boxes to fix a firmware issue... I thought it should be as simple as defining a package resource with the specific version set, ala: > # Need to install a new ker

[Puppet Users] Re: Installing a specific OL6 Kernel version...

2014-12-16 Thread Gavin Williams
OK, after a bit more experimentation, I managed to find a combination that worked: # Need to install a new kernel version - GW 16/12/14 > package { 'kernel-2.6.32-220.4.2.el6': > ensure => present > } Cheers Gav On Tuesday, 16 December 2014 15:20:18 UTC, Gavin Williams wrote: > > Afternoon a

[Puppet Users] Re: Firewall rule proto default

2014-12-16 Thread Laurence Foley
Thanks Thomas, That has done the trick. On Monday, December 15, 2014 10:16:44 AM UTC, Laurence Foley wrote: > > Opening this question that I posted on the ask site > > to a wider (?) audience: > > > > Quick question regard

[Puppet Users] Disabling a module on a particular node type ...

2014-12-16 Thread Matt Wise
We're using Puppet to build up a few docker containers, and we find that the puppetlabs-firewall module throws some errors during initial compilation. These errors are ignorable ... but they're obnoxious. Is there a way to explicitly disable a module from being parsed for a particular node type? D

Re: [Puppet Users] Windows Packages and DisplayName

2014-12-16 Thread Rob Reynolds
On Mon, Dec 15, 2014 at 8:09 PM, Mauricio Tavares wrote: > > Do you still need to use the DisplayName as the name of a package as > mentioned in > https://docs.puppetlabs.com/puppet/3.7/reference/resources_package_windows.html > ? > Yes. As long as you are using the built in package provider for

[Puppet Users] Re: trouble getting list of nodes via PE 3.7 Rest API

2014-12-16 Thread Russell Cecala
I guess I really don't need to list the nodes. I just wanted to try out the PE3.7 rest api. What I really need to be able to do is add nodegroups. I had been using the console rake api for this, but the console rake api is to be depreciated. I put the details of what I have tried, and what goes

[Puppet Users] Announce: Puppet Enterprise 3.7.1 is available

2014-12-16 Thread Geoff Nichols
Dear Puppet Enterprise Users, Puppet Enterprise 3.7.1 is now available. This is a bug-fix and security release of Puppet Enterprise. All users of Puppet Enterprise 3.x are encouraged to upgrade when possible to Puppet Enterprise 3.7.1. Puppet Enterprise 3.7.1 includes fixes to address security v

[Puppet Users] Re: Case Statement for setting IP addresses

2014-12-16 Thread James Taylor
Ok, I found the problem. On the line with: $addr=$net$ip Should look like this: $addr="$net$ip" Plus a quick "thank you" to Peter Bukowinski for the correction, I have clean running test code. -- James On Thursday, December 11, 2014 11:23:51 AM U

Re: [Puppet Users] puppetlabs-firewall & rate limit

2014-12-16 Thread Ciro Iriarte
El lunes, 15 de diciembre de 2014 13:30:48 UTC-3, Juan Sierra Pons escribió: > > 2014-12-15 17:19 GMT+01:00 Ciro Iriarte >: > > > Hi!, anybody know if it's possible to create a rule equivalent to this > with > > puppetlabs' firewall module?: > > > > iptables -I INPUT -i eth0 -p --dport -m h

Re: [Puppet Users] puppetlabs-firewall & rate limit

2014-12-16 Thread Juan Sierra Pons
Hi, I haven't used a similar rule on IPtables, so I don't know if the puppet one created is equivalent. So next step i think would be check different iptables output from the same rule. The one created by the command line and the one created by puppet. The steps would be 1.- Flush the iptables t