I'm actually having this exact same problem. In my hiera.yaml file I had a
hierarchy including two facts and then some strings derived from facter
facts.
When I run puppet agent --test the hiera vars in files named for the node's
$fqdn, etc. aren't found, but if I puppet apply specifying my sit
> I get the exact same error when I run Deepak's suggested command on
> RHEL 6, which includes ruby 1.8.7:
>
Yeeeah. Or at least if there is an issue that's not the way to figure it
out. Thanks for taking time to sanity check the diagnostic command.
When I asked about the same issue in #puppet so
jt/OI-151A-STABLE/151A-PRESTABLE7/newbuilds/sfw/proto/root_i386/usr/include
-I/home/jt/OI-151A-STABLE/151A-PRESTABLE7/newbuilds/sfw/proto/root_i386/usr/sfw/include
-I/home/jt/OI-151A-STABLE/151A-PRESTABLE7/newbuilds/sfw/proto/root_i386/usr/include
-I/home/jt/OI-151A-STABLE/151A-PRESTABLE7/newb
Hi all,
I'm having an issue on the master I'm using in my staging
environment with getting storeconfigs to work with puppetdb.
I should say up front that my staging environment is probably a little
uncommon. I'm running OpenIndiana which is a distribution of the open
source fork of OpenSolaris.