Installing 3.0.11 (and removing all the old versions manually, fucking ruby gems!) didn't help for me:
~$ sudo gem list *** LOCAL GEMS *** activemodel (3.0.11) activerecord (3.0.11) activesupport (3.0.11) arel (2.0.10) bigdecimal (1.1.0) builder (2.1.2) bundler (1.1.5) charlock_holmes (0.6.8) i18n (0.5.0) io-console (0.3) json (1.5.4) minitest (2.5.1) multi_json (1.3.6) puppet-lint (0.2.1) rake (0.9.2.2) rdoc (3.9.4) tzinfo (0.3.33) I think there used to be an ubuntu package for activerecord but it's not there anymore. On Thu, Oct 4, 2012 at 9:30 AM, Andy Parker <a...@puppetlabs.com> wrote: > I encountered this issue yesterday when trying to reproduce another > issue. I discovered that you need to be using activerecord 3.0.11. > Later versions don't seem to work (error with a "stack too deep") and > earlier versions don't seem to work (error with "uninitialized > constant ActiveRecord"). > > On Thu, Oct 4, 2012 at 7:55 AM, Jonathan Gazeley > <jonathan.gaze...@bristol.ac.uk> wrote: >> I managed to set up a fresh virtual machine with puppet 3 on it. Using the >> same server config and certs and a demo puppet 3 client, the system worked. >> So I wasn't able to run any debugging. >> >> Therefore, I am forced to conclude that the problem lies not with puppet 3 >> itself, but probably with some old gems that are left lying around on my old >> system. >> >> So I have a new plan: rather than upgrade my old puppetmaster from 2.7 to >> 3.0, I'll create a new puppet 3 server and migrate to that. Then I'll >> re-upgrade my old 2.7 puppetmaster and run the debugs... if you are still >> interested in them by then. >> >> Cheers, >> Jonathan >> >> >> >> On 04/10/12 12:34, Jonathan Gazeley wrote: >>> >>> Hi Eric, >>> >>> Thanks for your attention on this. >>> >>> Right now I'm not able to run any tests on my puppet master because we >>> were forced to roll it back to 2.7 to restore service. I work at a >>> university, this week is freshers' week and we totally need our config >>> management to work at this busy time! >>> >>> Hopefully in the next few days I'll try to set up a second puppet master >>> with puppet 3 and see if I can recreate the problem without breaking all >>> of my infrastructure ;) >>> >>> Cheers, >>> Jonathan >>> >>> >>> On 04/10/12 00:20, Eric Sorenson wrote: >>>> >>>> Thanks for reporting this, we're looking into it. I've made a ticket >>>> for your issue: https://projects.puppetlabs.com/issues/16770 >>>> >>>> If you can do so, could you please run the puppet master with the >>>> '--trace' option ( either on the command line or with a `ARGV << >>>> '--trace'` line in config.ru if you are starting from passenger, and >>>> update the ticket with the output? Thanks!! >>>> >>>> eric0 >>>> >>>> On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote: >>>> >>>> Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0. >>>> >>>> Since then, all puppet runs have been failing with this error: >>>> >>>> Error: Could not retrieve catalog from remote server: Error 400 on >>>> SERVER: Could not autoload puppet/indirector/node/active_record: >>>> uninitialized constant ActiveRecord >>>> >>>> >>>> My colleague and I have put a few hours into trying to work out >>>> what's >>>> wrong. rubygem-activerecord-2.1.1-2.el6.noarch is installed from the >>>> puppetlabs RPM repo. We've reinstalled all components but made no >>>> progress. >>>> >>>> I found this thread which seems to describe the same behaviour, but >>>> there are no replies: >>>> >>>> >>>> >>>> https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ >>>> >>>> >>>> >>>> <https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ> >>>> >>>> >>>> >>>> Anyone got any ideas? >>>> >>>> Thanks, >>>> Jonathan >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Puppet Users" group. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msg/puppet-users/-/KPQEZyWqezMJ. >>>> To post to this group, send email to puppet-users@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> puppet-users+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/puppet-users?hl=en. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
