Okay, looks like removing environment = master from the [master] block
fixed the issue..
I took that from this example
https://puppetlabs.com/blog/git-workflow-and-puppet-environments/ not sure
how/why it seemed to work fine for the rest of the configration with the
exception of hiera.
Than
Ygor, My common.yaml is actually empty at the moment.
I think I have discovered the problem...I found that it is using the
hiera.yaml file from my master environment instead of testing but I am not
sure why...
Here is my /etc/puppet/puppet.conf
[main]
# The Puppet log directory.
# Th
I have tried restarting puppet master
[root@puppetmaster ~]# service puppetmaster restart
Also, I have stopped the puppetmaster daemon and run it from the command
line:
[root@puppetmaster ~]# /usr/bin/puppet master -d --no-daemonize
Debug: hiera(): Hiera YAML backend starting
Debug: hiera(
Yes and it seems to work
[root@puppetmaster ~]# hiera classes -c
/etc/puppet/environments/testing/hiera.yaml environment=testing
role=webserver fqdn=node1 --debug -a
DEBUG: Wed Jun 05 10:02:23 -0600 2013: Hiera YAML backend starting
DEBUG: Wed Jun 05 10:02:23 -0600 2013: Looking up classes in
Ok maybe I spoke too soon...
It looks like the hiera hierarchy is not seeing the custom fact and as a
result is not applying the corresponding .yaml file. I expected it to load
the hieradata\webserver.yaml file. However as the puppetmasterd debug log
shows that it skips over this and loads the
That worked thanks!
On Tuesday, June 4, 2013 2:09:48 PM UTC-6, Keith Burdis wrote:
>
> You could set a custom "role" fact on node1 and node2 with the value
> "webserver" and then use the "role" fact in your Hiera hierarchy.
>
> For example using facter.d on on node1 and node2:
>
> # cd /etc/facte
Hi,
I am trying to use Hiera in puppet 3 and I have two nodes that both need
the same configuration. In this case they are two web servers which have
the same apache configuration.
Rather than creating two seperate hiera files for node1.yaml and node2.yaml
is there a way to group these by rol