Puppet 4.9.0 just went live and we are waiting for the proper release
notes to be sent out.
Early users have started to upgrade and have been running into a couple
of issues that are easily fixable.
The new implementation is sensitive to errors in hiera.yaml
------------------------------------------------------------
If you see a "expected Hash, got Boolean", or "expected Hash got
String", it is most likely because your hiera.yaml file is empty.
If you want it to be empty, modify it to have an empty :hierarhy hash
instead. Or move it out of the way and get the defaults.
There will be an improvement in PUP 4.9.1 where an empty hiera.yaml will
not error in this way. See Jira ticket PUP-7164).
The new implementation reads and uses a hiera.yaml in the root of
an environment.
------------------------------------------------------------------
If you get the error "a hiera.yaml version 3 cannot be used in an
environment" means that puppet found a hiera.yaml in the root of an
environment, and that is taken as an opt in to hiera 5's "data in
environment" feature.
For example, you may have .../environments/production/hiera.yaml
That file used to have no meaning (just being a copy placed there).
It is now significant. Fix the issue by moving it out of the way
(rename, or delete). Those that use this pattern to symlink to the real
global hiera.yaml need to rethink if they want to continue doing so.
The real solution is to use the features in hiera 5 and actually keep
the configuration in the environment.
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
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/o6vksi%24ho6%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
