I'm trying to set up hiera for the first time, and something really odd is
happening.
I set up my hiera.yaml file in /etc/puppet/, and it was pretty simple:
---
:backends:
- yaml
:hierarchy:
- "%{hostname}"
- common
:yaml:
:datadir: /etc/puppet/data
So I added a "flag" class, which just has a manifest containing one
"notify" so I can see that it's getting loaded. I stuck it in
"data/common.yaml":
---
puppetserver : 'zgepetto.foo.net'
ipamaster : 'ipamaster'
classes:
- role::base
- flag
And lo and behold, the notify showed up when I ran puppet agent -t --noop.
Then I tried moving the flag mention into a file named for my test node,
zw129.yaml:
---
classes:
- role::workstation
- flag
But the flag never got picked up. Confused, I moved it back to common.yaml
and there it was again. Eventually, I got around to removing "common" from
my hiera.yaml file (leaving only the "{hostname}" in the hierarchy) and
still common is getting loaded, even after doing a "service puppetmaster
restart".
I've looked around for other instances of hiera.yaml but don't see any.
What else could be causing hiera to load a common.yaml that I'm not asking
for, and neglecting the zw129.yaml that I am asking for? It sure feels like
I'm picking up an incorrect config file somewhere, but I'm not sure where
to look or what logfile to examine next.
Thanks!
*
*
*Bret Wortman*
http://damascusgrp.com/
http://about.me/wortmanbret
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
