That is correct, when those values are not found, hiera doesn't search those tiers at all. The debug information could be more helpful about it, though.
Rob Nelson rnels...@gmail.com On Tue, Jul 19, 2016 at 1:27 PM, Gavin Williams <fatmc...@gmail.com> wrote: > John > > I'm pretty sure when you're running hiera on the command line, you need to > 'provide' the fact values. See > https://docs.puppet.com/hiera/3.2/command_line.html#fact-sources > > HTH > > Gav > > > On Tuesday, 19 July 2016 18:14:55 UTC+1, John Baird wrote: >> >> All files should be readable as they are either 755 or 644. Even if they >> don't exist, hiera should still attempt to "Search" that path and show me >> what directories it is searching when doing so with debug on. Since it is >> not showing the directories with variables, it, for some reason, is >> skipping them alltogether. >> >> another example: >> >> --- >> :backends: >> - yaml >> :yaml: >> :datadir: "/opt/local/modules/hieradata" >> :hierarchy: >> - common1/%{calling_class} >> - common2/%{calling_class} >> - common3 >> - puppet_test >> >> hiera -d 'dhcpd::package_name' environment=production >> DEBUG: 2016-07-19 13:12:49 -0400: Hiera YAML backend starting >> DEBUG: 2016-07-19 13:12:49 -0400: Looking up dhcpd::package_name in YAML >> backend >> DEBUG: 2016-07-19 13:12:49 -0400: Looking for data source common3 >> DEBUG: 2016-07-19 13:12:49 -0400: Cannot find datafile >> /opt/local/modules/hieradata/common3.yaml, skipping >> DEBUG: 2016-07-19 13:12:49 -0400: Looking for data source puppet_test >> DEBUG: 2016-07-19 13:12:49 -0400: Cannot find datafile >> /opt/local/modules/hieradata/puppet_test.yaml, skipping >> nil >> >> common1 and common2 are completely ignored. >> >> On Tuesday, July 19, 2016 at 5:48:59 AM UTC-5, Rob Nelson wrote: >>> >>> It cannot find the files. Do they exist and are they readable to the >>> user you are running hiera/the puppet master service as? >>> >>> On Monday, July 18, 2016, John Baird <john.w...@gmail.com> wrote: >>> >>>> Attempting to use hiera to hold all of my node-specific variables. It >>>> has been some time since I have run a puppet server, but I know it's not >>>> THAT hard. That being said, my modules run fine, but hiera is not looking >>>> them up correctly. It appears that any lines that contain any variables in >>>> the hiera.yaml are ignore and are not searched. Any assistance would be >>>> great! I'm sure it's something small, but sooooooo confused... >>>> >>>> >>>> HIERA.YAML >>>> ------------------ >>>> --- >>>> :backends: >>>> - yaml >>>> :yaml: >>>> :datadir: "/opt/local/modules/hieradata" >>>> :hierarchy: >>>> - '%{calling_module}/%{::hostname}' >>>> - '%{calling_module}/common' >>>> - common >>>> >>>> >>>> hiera -d 'dhcpd::package_name' environment=production >>>> DEBUG: 2016-07-18 20:48:38 -0400: Hiera YAML backend starting >>>> DEBUG: 2016-07-18 20:48:38 -0400: Looking up dhcpd::package_name in >>>> YAML backend >>>> DEBUG: 2016-07-18 20:48:38 -0400: Looking for data source common >>>> DEBUG: 2016-07-18 20:48:38 -0400: Cannot find datafile >>>> /opt/local/modules/hieradata/common.yaml, skipping >>>> nil >>>> >>>> >>>> --- >>>> :backends: >>>> - yaml >>>> :yaml: >>>> :datadir: "/opt/local/modules/hieradata" >>>> :hierarchy: >>>> - '%{calling_module}/%{::hostname}' >>>> - '%{calling_module}/common' >>>> - common >>>> - puppet_test >>>> >>>> hiera -d 'dhcpd::package_name' environment=production >>>> DEBUG: 2016-07-18 20:49:30 -0400: Hiera YAML backend starting >>>> DEBUG: 2016-07-18 20:49:30 -0400: Looking up dhcpd::package_name in >>>> YAML backend >>>> DEBUG: 2016-07-18 20:49:30 -0400: Looking for data source common >>>> DEBUG: 2016-07-18 20:49:30 -0400: Cannot find datafile >>>> /opt/local/modules/hieradata/common.yaml, skipping >>>> DEBUG: 2016-07-18 20:49:30 -0400: Looking for data source puppet_test >>>> DEBUG: 2016-07-18 20:49:30 -0400: Cannot find datafile >>>> /opt/local/modules/hieradata/puppet_test.yaml, skipping >>>> nil >>>> >>>> -- >>>> 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+unsubscr...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/puppet-users/34a20f55-02a2-49c7-88d2-28885636dab2%40googlegroups.com >>>> <https://groups.google.com/d/msgid/puppet-users/34a20f55-02a2-49c7-88d2-28885636dab2%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> -- >>> >>> Rob Nelson >>> rnel...@gmail.com >>> >>> -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/93956c01-6dd7-4b44-b535-d6e31e22693d%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/93956c01-6dd7-4b44-b535-d6e31e22693d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAC76iT9QR_JGoF73Z8BHVE70xHXZ7huFxikOaUcOFKnr5b38Zw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
