Issue #2041 has been updated by Peter Meier. Assigned to set to James Turnbull
James Turnbull wrote: > Turned out to a multiple versions of ActiveRecord installed. hmm can you remember how you came to this conclusion? Yesterday we tried to bootstrap a 0.24.8 puppetmaster in passenger with REE, everything was working fine except stored configs, as Puppet failed to load rails, hence Puppet.features.rails? was false. However latest rails (2.3.something) have been installed in the REE environment and only 1 rails version have been installed in the REE environment. For sure there have been another version in the system environemnt, however imho REE shouldn't look at them at all, so should puppet startet with REE. We could fix this issue by adding the same requires as mentioned above to the rails.rb If you prefer we could do another test with REE and 0.25.0 to see if the problem still remains. ---------------------------------------- Bug #2041: Rails error with upgraded system packages?, even with storeconfigs = false http://projects.reductivelabs.com/issues/2041 Author: Robin Powell Status: Closed Priority: Normal Assigned to: James Turnbull Category: Target version: unplanned Complexity: Unknown Affected version: 0.24.7 Keywords: I'm not sure what I upgraded on my system to cause this (I run apt-get upgrade or so routinely), but now: $ puppetd -tv Failed to load feature test for rails: undefined method `synchronize' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class info: Retrieving plugins err: Could not retrieve catalog: Rails is missing; cannot store configurations warning: Not using cache on failed catalog $ If I set storeconfigs to false, the run occurs but the error still does too: $ puppetd -tv Failed to load feature test for rails: undefined method `synchronize' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class info: Retrieving plugins info: Caching catalog at /var/lib/puppet/state/localconfig.yaml notice: Starting catalog run notice: Finished catalog run in 9.99 seconds $ Downgrading rails (via dpkg) from 2.1.0-6 to 2.0.2-2 did not seem to make the error go away. Puppet is 0.24.7 -Robin -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
