Issue #16770 has been updated by Josh Cooper. Status changed from Needs More Information to Closed
Joe, Jonathan, we haven't received any more reports on this issue, so we're pretty confident it's a rubygems configuration issue. I'm going to close this ticket for now, but if you run into the problem, feel free to reopen. ---------------------------------------- Bug #16770: "uninitialized constant ActiveRecord" on puppet 3 w/ storedconfigs https://projects.puppetlabs.com/issues/16770#change-74972 Author: eric sorenson Status: Closed Priority: Normal Assignee: Category: Target version: 3.0.x Affected Puppet version: 3.0.0 Keywords: Branch: Two users on the mailing list reported the same error loading active record on Telly: https://groups.google.com/d/topic/puppet-users/3tC0gYg9XA0/discussion One is on EL6, the other Ubuntu 10.4 <pre> 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. </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
