Turns out that the problem was fixed by restarting puppetmaster. I
hadn't appreciated that this is necessary when the hiera config changes
- as you don't need to restart puppetmaster to pick up new manifests,
for instance.
Thanks for your help anyway!
Jonathan
On 10/05/13 16:47, Jon Ward wro
Try putting the variable in common.yaml at the bottom of the hierarchy and
see if it gets picked up. If it does then perhaps the value of the fqdn
fact isn't what you think it is.
You can also try running puppetmaster in the foreground in debug mode:
$ puppet master —no-daemonize —debug
Now w
Hi Jon,
Thanks for your tip. I had made a typo in my yaml which debug mode
picked up. I fixed it, and now your command works when run on the
puppetmaster but the same error persists when the variable is accessed
either from a manifest or from a template during a puppet agent run.
I'm wonderi
Hi,
Have you tried doing the Hiera lookup on the command line to double check
it can be read?
$ hiera -d -c /path/to/hiera.yaml jrs_config_server1 fqdn=hostname
>
Cheers,
Jon
On Friday, May 10, 2013 12:18:22 PM UTC+1, Jonathan Gazeley wrote:
>
> Hi,
>
> I'm having a problem accessing Hiera d
