Issue #9290 has been updated by Patrick Buckley.
With the sql injection vuln in older versions of active record 3.x this has become an issue for us. activerecord 3.2.5 puppet 2.7.14 puppet dashboard 1.2.8 puppetmaster --- notice: Compiled catalog for in environment production in 4.45 seconds info: Caching catalog for debug: Searched for resources in 0.00 seconds debug: Searched for resource params and tags in 0.00 seconds debug: Resource removal in 0.00 seconds debug: Resource merger in 0.00 seconds err: stack level too deep puppet agent --- err: Could not retrieve catalog from remote server: Error 400 on SERVER: stack level too deep warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Another relevant note this doesn't happen on all of our nodes. Only on nodes created after the active record upgrade so far. ---------------------------------------- Bug #9290: Puppet master fails with 'stack level too deep' error when storeconfigs = true with rails stack 3.1.0 https://projects.puppetlabs.com/issues/9290#change-64488 Author: Mark Stanislav Status: Accepted Priority: High Assignee: Category: Rails Target version: Affected Puppet version: 2.7.3 Keywords: storeconfigs rails activerecord 3.1.0 Branch: Out of nowhere, a known-working Puppet stack build script started to fail. The tell-tale error is 'stack level too deep' which from other historical bug reports always seems related to Ruby directly. After many hours of digging around, I checked for updated gem versions on the system. There was an update to rails 3.1.0 (and activerecord, etc.) which apparently is breaking the Puppet master when working with storeconfigs = true. Disabling storeconfigs immediately works as expected again. When reverting from rails and friends 3.1.0 to 3.0.10, Puppet again works as expected. I don't have any insight into where exactly this is all failing, only the version which is causing the issue and the condition to emulate it. This was only tested again Puppet 2.7.3 using the gem install with both webrick and Apache+Passenger. Attached is a debug output. -- 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.
