On 2018-09-19 17:41,
ch...@fuzzyblender.com wrote:
> Hi Sean,
>
> I'm having the same issue, and I see what you said, I'm just too new to
> puppet. Would it be possible for you (or others) to expand on how you
> fixed this (with and example)?
>
> Chris
>
I had responded to Sean in an email - reposting it here now:
How did you run `puppet lookup` ?
If you gave it a node with --node it will use the stored facts for that
node, otherwise you have to give it the facts to use for that node.
If not specifying a --node, lookup will use the facts for the host where
you are running `puppet lookup`.
Maybe that is what is tricking you?
Try running with `puppet apply --debug` when testing - that turns on
logging of --explain from all lookups including those made via APL.
When you do that, are the path's set?
Still having weird problems? Check your axioms - are you running the
expected file in the expected environment etc.
- henrik
> Module"test"DataProvider(hiera configuration version 5)
> Using configuration
> "/etc/puppetlabs/code/environments/production/modules/test/hiera.yaml"
> Hierarchy entry "Full Version"
> Path"/etc/puppetlabs/code/environments/production/modules/test/data/-.yaml"
> Original path:"%{
facts.os.name
> <
http://facts.os.name>}-%{facts.os.release.full}.yaml"
> Pathnot found
> Hierarchy entry "Major Version"
> Path"/etc/puppetlabs/code/environments/production/modules/test/data/-.yaml"
> Original path:"%{
facts.os.name
> <
http://facts.os.name>}-%{facts.os.release.major}.yaml"
> Pathnot found
> Hierarchy entry "Distribution Name"
> Path"/etc/puppetlabs/code/environments/production/modules/test/data/.yaml"
> Original path:"%{
facts.os.name <
http://facts.os.name>}.yaml"
> Pathnot found
> Hierarchy entry "Operating System Family + Major Version"
> Path"/etc/puppetlabs/code/environments/production/modules/test/data/-.yaml"
> Original path:"%{facts.os.family}-%{facts.os.release.major}.yaml"
> Pathnot found
> Hierarchy entry "Operating System Family"
> Path"/etc/puppetlabs/code/environments/production/modules/test/data/.yaml"
> Original path:"%{facts.os.family}.yaml"
> Pathnot found
> Hierarchy entry "common"
> Path"/etc/puppetlabs/code/environments/production/modules/test/data/common.yaml"
> Original path:"common.yaml"
> No such key:"test::dconf_default_config"
>
> |
>
> See how all the Hierarchy Paths have bad file names? This leads
> me to think that somehow Hiera has lost the ability to parse
> facts in my feature branch of this module. If I check the
> master branch out for the "test" module then Hiera produces the
> correct datafile names.
>
> How can that be?
>
> --
> 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
puppet-users...@googlegroups.com
> <mailto:
puppet-users...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/puppet-users/f97ce708-9ce8-43f4-bb92-2400cfaf9d82%40googlegroups.com
> <
https://groups.google.com/d/msgid/puppet-users/f97ce708-9ce8-43f4-bb92-2400cfaf9d82%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit
https://groups.google.com/d/optout.
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/