On Wednesday, March 27, 2013 11:29:30 AM UTC-7, Philip Brown wrote: > > > I set up a /etc/puppet/hiera.yaml, pointing to a special hieradata > directory...but clients were not seeing the values I populated. >
First off, check Puppet's hiera_config setting (http://docs.puppetlabs.com/references/3.1.1/configuration.html#hieraconfig) -- is there a value in your puppet.conf? What happens if you explicitly point it at your hiera.yaml file? Next, double-check the syntax of your hiera.yaml file. (http://docs.puppetlabs.com/hiera/1/configuring.html) Are you forgetting the leading colon on :hierarchy:? > > The only way it found any hiera-set value, was if I put it in > /var/lib/hiera/common.yaml > > Which is rather odd, because the autogenerated /etc/hiera.yaml does not > mention "common". it mentions "global". > "Common" is in the default settings Hiera uses if the config file is empty or is missing keys. http://docs.puppetlabs.com/hiera/1/configuring.html#default-config-values Since "global" isn't being used, that proves that Hiera isn't reading /etc/hiera.yaml. Either the hiera_config setting is pointing it somewhere unexpected, or the format of your hiera.yaml is off, and it's interpreting that config as missing a :hierarchy: setting. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
