On Wed, Jan 9, 2019 at 9:06 AM Peter Berghold
wrote:
> Hi folks,
>
> I know... I know... get off of Puppet 3. I'll be getting there soon.
>
> Right now I have Puppet 3 in our production environment where I work.
> Long political story as to why we are still on 3 that I won't get into. I
> just
Hi folks,
I know... I know... get off of Puppet 3. I'll be getting there soon.
Right now I have Puppet 3 in our production environment where I work. Long
political story as to why we are still on 3 that I won't get into. I just
did a release of the Puppet code and one of the "features" of the
Just delved into my history :
Do not forget to set this VAR :
export RUBYLIB=/var/lib/puppet/lib/
facter --yaml > /tmp/facter.yaml to generate a yaml file of the facts,
which can be passed to hiera.
hiera --debug --config /etc/puppet/hiera.yaml test -y /tmp/facter.yaml
or just passing a sin
Hi,
Run the master in no-daemonize and debug. You will see how it searches through
your hierarchy that way.
Also you can use the command line on the master to query hiera. See puppet docs
for details.
Cheers,
Den
On 01/05/2013, at 2:46, lth wrote:
> I'm using puppet 3.1 and I want to figure
I'm using puppet 3.1 and I want to figure out why hiera seems to be looking
in the wrong place and getting the wrong value.
I found a post from this group saying to run puppet -d on the master and
look in the log. Having done that I still don't see anything hiera related
except for where puppe
I just installed puppet 3 (3.0.0-0.1rc3puppetlabs1) on a 32bit Ubuntu 12.04
'server' VM. I used the packages for the install.
I then copied over my existing modules and manifests from my production
2.7.x puppet master, and also my hiera.yaml and hieradata/*.
When I run puppet agent --test I get
