Re: [Puppet Users] Unreported Windows nodes (Puppet 3.7.3, Exchange 2010)

2015-02-11 Thread cko
I just updated to 3.7.4 This is the output when I manually run Puppet: http://i.imgur.com/pdrklFm.png (Still, only happening on exchange 2010 nodes) The Agent basically stops working after loading all facts, without removing the .lock file. Let me know if you need more information on this.

Re: [Puppet Users] Re: Is there a better way to limit module actions based on facts?

2015-02-11 Thread leam hall
On Wed, Feb 11, 2015 at 4:18 PM, Joseph Karns wrote: > Hello Leam: > > I think your looking for something like this: > > - > > define sysusers::setup( > $hash > ) { > > > case $::osfamily { > 'redhat': { > $user_home = '/home' > } >

Re: [Puppet Users] Re: Is there a better way to limit module actions based on facts?

2015-02-11 Thread Joseph Karns
Hello Leam: I think your looking for something like this: - define sysusers::setup( $hash ) { case $::osfamily { 'redhat': { $user_home = '/home' } 'solaris': { $user_home = '/export/home' }

Re: [Puppet Users] Re: Is there a better way to limit module actions based on facts?

2015-02-11 Thread leam hall
Hey all, I'm still getting stuck, and I've moved the case statement to several places. The issue is the module's init.pp calls setup.pp. The user data is stored in Hiera. So far I've tried: 1. Going between $osfamily, $::osfamily, ${osfamily}, {$osfamily}, and ${::osfamily}. The failures seem to

Re: [Puppet Users] Re: Is there a better way to limit module actions based on facts?

2015-02-11 Thread Garrett Honeycutt
On 2/11/15 7:33 PM, Joseph Karns wrote: > Leam: > > The reason you are getting the 400 Error is because you don't have > $osfamily defined. > > You can write your case statement as such: > > case $::osfamily { >'redhat': { > # do something RHEL specific >} >'debian': { > #

[Puppet Users] Re: Is there a better way to limit module actions based on facts?

2015-02-11 Thread Joseph Karns
Leam: The reason you are getting the 400 Error is because you don't have $osfamily defined. You can write your case statement as such: case $::osfamily { 'redhat': { # do something RHEL specific } 'debian': { # do something Debian specific } default: { # ... }

Re: [Puppet Users] Announce: Puppet Server 1.0.2 available!

2015-02-11 Thread Trevor Vaughan
Nice! Thanks. Trevor On Tue, Feb 10, 2015 at 1:44 PM, Kevin Corcoran < kevin.corco...@puppetlabs.com> wrote: > On Sun, Jan 25, 2015 at 5:07 PM, Trevor Vaughan > wrote: > >> I've been able to do everything from the APIs thus far and, yes, having a >> 'puppet master reload' and 'puppet master env

[Puppet Users] Allowing duplicate namevars in custom types

2015-02-11 Thread jwilkicki
Hi all! I'm working on a custom type that applies xpaths to files. I expect the interface to look something like: xpath { "some update": xpath => "/some/xpath", command => "replace", value => "newvalue", file => "/path/to/file.xml" } I'm having a little trouble picking

Re: [Puppet Users] Re: representing undef in hiera?

2015-02-11 Thread James Olin Oden
Never, mind I was looking in the wrong place. It's in the YAML spec (or it's a YAML thing). Tilde represents NULL (or is equivalent too): http://www.yaml.org/spec/1.2/spec.html#id2805071 Thanks...James On Wed, Feb 11, 2015 at 11:01 AM, James Olin Oden wrote: > Hey Clayton is this documen

Re: [Puppet Users] Re: representing undef in hiera?

2015-02-11 Thread James Olin Oden
Hey Clayton is this documented somewhere (i.e. the us of ~ like this, or the use of ~ as a value in hiera file?). Thanks...James On Wed, Feb 11, 2015 at 10:53 AM, Clayton O'Neill wrote: > In my experience using tilde as the value will pass through the equivalent > of undef. That said, I agree

[Puppet Users] Re: Is there a better way to limit module actions based on facts?

2015-02-11 Thread leam hall
Trying to use a case statement with a setup.pp file that uses hiera and parameters. We have pulled a module from the forge and are trying to make it fit our needs. The issue I'm trying to resolve is to have the user's home directories created on /home/$user on Red hat systems and /export/home/

[Puppet Users] Re: representing undef in hiera?

2015-02-11 Thread Clayton O'Neill
In my experience using tilde as the value will pass through the equivalent of undef. That said, I agree with all the comments about making optional arguments actually optional, and not forcing them to be defined in hiera. For example: --- key: ~ -- You received this message because you are s

Re: [Puppet Users] Re: representing undef in hiera?

2015-02-11 Thread jcbollinger
On Tuesday, February 10, 2015 at 9:48:50 AM UTC-6, Christopher Wood wrote: > > On Tue, Feb 10, 2015 at 06:52:05AM -0800, jcbollinger wrote: > >On Monday, February 9, 2015 at 10:37:39 AM UTC-6, Christopher Wood > wrote: > > > > > > I'm dealing with a config file template where m

[Puppet Users] Re: facter error esolved to an invalid value

2015-02-11 Thread Robert Reilly
Tried upgrading facter on that node, but same error ... On Wednesday, February 11, 2015 at 8:04:18 AM UTC-5, Robert Reilly wrote: > > All, I am getting the following problem with facter on 5 of my nodes, > Fact resolution fact='enviro', resolution='' resolved to an > invalid value: Expected (?-m

[Puppet Users] Is there a better way to limit module actions based on facts?

2015-02-11 Thread Joseph Karns
Hello Lean: The way to handle this the best is exactly what you did. OS level specifications should be made at the module level. I have seen some try to handle mixed environments with the heira hierarchy, but this makes the modules you build less portable. you would also need to create multipl

[Puppet Users] facter error esolved to an invalid value

2015-02-11 Thread Robert Reilly
All, I am getting the following problem with facter on 5 of my nodes, Fact resolution fact='enviro', resolution='' resolved to an invalid value: Expected (?-mix:xxx(vs|sv).{2,7}\d{1,2}) to be one of [Integer, Float, TrueClass, FalseClass, NilClass, String, Array, Hash], but was Regexp, this seem