Issue #9290 has been updated by Charlie Sharpsteen.

Keywords changed from storeconfigs rails activerecord 3.1.0 to storeconfigs 
rails activerecord 3.1.0 customer

----------------------------------------
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-88598

* Author: Mark Stanislav
* Status: Accepted
* Priority: High
* Assignee: eric sorenson
* Category: Rails
* Target version: 3.1.x
* Affected Puppet version: 2.7.3
* Keywords: storeconfigs rails activerecord 3.1.0 customer
* 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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to