Tim, this is a very odd message that you're getting.
The reason I say so is that code is from the old hiera-puppet, and it
was removed from hiera-puppet before the 1.0.0 release (here's the
pull request: https://github.com/puppetlabs/hiera-puppet/pull/11), and
as such was never part of hiera-puppe
In regard to: [Puppet Users] error testing puppet 3.x upgrade: You need...:
All-
Does anyone have any thoughts on what's causing this issue?
Since I posted the original question, I've also tried starting with
a fresh RHEL 6.5 system that's never had puppet on it, and installed 3.4.2
from Puppet
In regard to: Re: [Puppet Users] error testing puppet 3.x upgrade: You need...:
Any chance you have a symlink to
/usr/lib/ruby/site_ruby/1.8/hiera/backend/ (or something similar) floating
around in your /var/lib/puppet? This was a common way to get Hiera to work in
Puppet 2.7 before the neces
Any chance you have a symlink to
/usr/lib/ruby/site_ruby/1.8/hiera/backend/ (or something similar)
floating around in your /var/lib/puppet? This was a common way to get
Hiera to work in Puppet 2.7 before the necessary glue was built into
3.x. If you do, remove it and restart.
Ramin
On 1/8/2
All-
I've been struggling with this all afternoon, so it's time to ask for
some help.
The TL;DR version:
On a 2.7.14 puppet client promoted to be a test 3.4.2 master, whenever a
client connects I get:
Warning: Puppet.features.rubygems? is deprecated. Require rubygems in your
application's ent
