On 23/06/16 07:45, chris wrote:
On Thursday, 23 June 2016 11:06:54 UTC+10, chris wrote:
So as you can see from above, it prefixes each keyname with the dir and
appends '.json', as it should BUT only if keyname/data src has a numeric
digit in it! Is this a bug in puppet??
Or am I missing someth
On Thursday, 23 June 2016 11:06:54 UTC+10, chris wrote:
So as you can see from above, it prefixes each keyname with the dir and
appends '.json', as it should BUT only if keyname/data src has a numeric
digit in it! Is this a bug in puppet??
Or am I missing something?
--
You received this mess
So, here's a bit more of the debug o/op:
Debug: Performing a hiera indirector lookup of icinga_servers with options
{:variables=>Scope(Class[main]),
:merge=>#>,
@value_type=#]>>>]>, @options={}>}
Debug: hiera(): Looking up icinga_servers in JSON backend
Debug: hiera(): Looking for data source p
Dang; wanted to add to my last..
Anyway, ran 'facter -p' on the node and those values are filled correctly.
How can I check what the master sees when the node checks in?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this
Yes, nt_location is 'sac', so sac.json as mentioned.
Not sure how to check the 'value' of that var... %{nt_location}. This is a
bit new to me.
Should have mentioned its copied from a working(!) 3.2 master; want to
'upgrade' with minimal changes.
--
You received this message because you are subs
You would need to have sac in your hiera.yaml hierarchy unless you are
defining this somewhere in a variable? Is that what nt_location is? Also,
if you changed hiera.yaml, you have to restart puppetserver.
On Monday, June 20, 2016 at 7:52:21 AM UTC-5, chris wrote:
>
> Given this /etc/puppetlab
