Issue #2041 has been updated by rlpowell.
Ummmm. I hardly know where to start. I apologize if this isn't as polite as it should be, but I've just left my job after a very hard several weeks. I love puppet, and want to help. > You've definitely got storeconfigs enabled here, even if you don't realize > it, and that's why you're getting that error. [email protected]> ack -a storeconfig /etc/puppet /etc/puppet/puppet.conf 13:storeconfigs = false [email protected]> So if it's enabled, I have no idea where. Having said that, however: when I set "storeconfigs = true", restart everything, set "storeconfigs = false", restart everything again, I get this error. A few hours later, it *does* stop. I'm sorry, I forgot to say that. So I guess it is somehow being stored somewhere? I don't know. That's not the big issue here, though, the big issue is: Furthermore, you apparently missed my point: with "storeconfigs = true", puppet *does not run at all*. Not even a little. Nothing. Total fail. Kaboom. On all clients. > I think the system is behaving as expected, other than that it's not > compatible with the version of Rails you're running. How is totally failing to function "as expected", exactly? If it's not compatible with the version of Rails I'm running, *please* tell me what version to use! As I said before: > Downgrading rails (via dpkg) from 2.1.0-6 to 2.0.2-2 did not seem to make the > error go away. I have no idea what i need to do to make this work again. I have no idea why it stopped working. I want to use storeconfigs, but if I turn it on, puppet fails, and I have no idea what to do about it. -Robin ---------------------------------------- Bug #2041: Rails error with upgraded system packages?, even with storeconfigs = false http://projects.reductivelabs.com/issues/2041 Author: rlpowell Status: Needs more information Priority: Normal Assigned to: Category: Target version: 0.24.8 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 -~----------~----~----~----~------~----~------~--~---
