There is indeed a global hiera.yaml file:
# cat /etc/puppetlabs/puppet/hiera.yaml
---
# Hiera 5 Global configuration file
version: 5
# defaults:
# data_hash: yaml_data
# hierarchy:
# - name: Common
#data_hash: yaml_data
hierarchy: []
Top level environment hiera looks good:
# cat
In this case it is hiera.
Can you please check:
- that there is no global hiera.yaml file in /etc/puppetlabs/puppet/hiera.yaml
or, that the data paths mentioned in that file are empty
- that node is the top level environment in your environment hiera.yaml file
Thanks again Martin,
I've changed the code as per recommended. However, the same issue still
persists. I'm starting to think that the issue is not code related but
lies elsewhere
# puppet agent --no-daemonize --onetime --verbose
Info: Using configured environment 'production'
Info:
Hi Dan,
I would write the grubipv6disable class in another way:
class grubipv6disable (
Boolean $enable,
) {
if $enable {
contain grubipv6disable::config
}
}
And keep the grubipv6disable::config class as is:
class grubipv6disable::config (
){
if $facts['os']['release']['major'] =~
You can use the puppet lookup command with the explain flag to see what is
being returned.
https://puppet.com/docs/puppet/6.17/hiera_automatic.html#using_puppet_lookup
On Mon, Sep 28, 2020, 6:03 AM djc...@gmail.com wrote:
> Thanks for that Martin,
>
> I seem to have unearthed a different
Thanks for that Martin,
I seem to have unearthed a different issue:
# puppet agent --no-daemonize --onetime --verbose
Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
Server Error: Evaluation Error: Error while evaluating a Resource
Statement, Class[Grubipv6disable]:
