Hi Jonathan, It appears that dhoppe/puppet actually ships an entire copy of hiera 1.0.0 and hiera-puppet inside its lib directory, which is unfortunate since hiera is now at 1.3.1 and hiera-puppet is part of puppet proper. I filed an an issue against the github repo, since this isn't an ideal approach, to say the least.
On Mon, Jan 20, 2014 at 8:16 AM, Jonathan Gazeley <jonathan.gaze...@bristol.ac.uk> wrote: > I fixed my own problem. Seems that when I installed dhoppe/postfix, and it > automatically included a dependency dhoppe/puppet which seems to have > overwritten some components of puppet. I immediately removed dhoppe/postfix > but didn't notice that dhoppe/puppet was still in situ. Removing this and > doing "sudo yum reinstall puppet" put back the files and it now works again. > > Cheers, > Jonathan > > > > On 20/01/14 12:19, Jonathan Gazeley wrote: > > Hi chaps, > > This morning I started running into an error. All my nodes started failing > with: > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > You need rubygems to use Hiera at > /home/ispms/PUPPETROOT/environments/common/modules/uob_ntp/manifests/init.pp:5 > on node dhcp-dev.nomadic-core.bris.ac.uk > > The master log shows: > > Jan 20 12:08:38 puppet-prod puppet-master[30673]: Puppet.features.rubygems? > is deprecated. Require rubygems in your application's entry point if you > need it. > Jan 20 12:08:38 puppet-prod puppet-master[30673]: (at > /usr/lib/ruby/site_ruby/1.8/puppet/util/feature.rb:17:in `add') > > I also read this recent thread, and none of the recommendations helped: > > http://grokbase.com/t/gg/puppet-users/1419xmhyf3/error-testing-puppet-3-x-upgrade-you-need-rubygems-to-use-hiera > > This morning a colleague of mine wrote a custom function. It looked sane to > me but I removed it in case it was broken, and it didn't help. > > I also installed a Forge module, which I later removed, and it didn't help. > > I'm running stock puppet-3.4.2 from the PL repo and we are using > hiera-1.3.0. Everything worked normally until this morning and I'm not > entirely sure where to go from here. Any suggestions of things to look at? > > Cheers, > Jonathan > > > -- > 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/52DD4BCB.30106%40bristol.ac.uk. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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/CA%2B421Wa_8-jb8DNTBGSONEHYqbroW4pN4hvvpca9%2B4uC8%2Btx%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
