Bug #2463
Puppet 0.24.8 does not work with Rails 2.3.2
| Status: | Duplicate | Start date: | 07/29/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Rails | |||
| Target version: | - | |||
| Affected Puppet version: | 0.24.8 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
The system is a Gentoo system with Ruby 1.8.7. When running puppetmasterd with —trace the following is produced when it tries to initialize rails.
Downgrading to Rails 2.2.2 fixed the issue.
err: Rails is missing; cannot store configurations /usr/lib64/ruby/site_ruby/1.8/puppet/parser/interpreter.rb:43:in `initialize' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:80:in `new' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:80:in `create_interpreter' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:37:in `interpreter' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:68:in `compile' /usr/lib64/ruby/site_ruby/1.8/puppet/util.rb:180:in `benchmark' /usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/core_ext/benchmark.rb:10:in `realtime' /usr/lib64/ruby/site_ruby/1.8/puppet/util.rb:179:in `benchmark' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:66:in `compile' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:21:in `find' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:210:in`find' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector.rb:49:in `find' /usr/lib64/ruby/site_ruby/1.8/puppet/network/handler/master.rb:65:in `getconfig' /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `to_proc' /usr/lib64/ruby/site_ruby/1.8/puppet/network/xmlrpc/processor.rb:52:in `call' /usr/lib64/ruby/site_ruby/1.8/puppet/network/xmlrpc/processor.rb:52:in `protect_service' /usr/lib64/ruby/site_ruby/1.8/puppet/network/xmlrpc/processor.rb:85:in `setup_processor' /usr/lib64/ruby/1.8/xmlrpc/server.rb:338:in `call' /usr/lib64/ruby/1.8/xmlrpc/server.rb:338:in `dispatch' /usr/lib64/ruby/1.8/xmlrpc/server.rb:325:in `each' /usr/lib64/ruby/1.8/xmlrpc/server.rb:325:in `dispatch' /usr/lib64/ruby/1.8/xmlrpc/server.rb:368:in `call_method' /usr/lib64/ruby/1.8/xmlrpc/server.rb:380:in `handle' /usr/lib64/ruby/site_ruby/1.8/puppet/network/xmlrpc/processor.rb:44:in `process' /usr/lib64/ruby/site_ruby/1.8/puppet/network/xmlrpc/webrick_servlet.rb:68:in `service' /usr/lib64/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/lib64/ruby/1.8/webrick/httpserver.rb:65:in `run' /usr/lib64/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib64/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib64/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib64/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib64/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib64/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib64/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib64/ruby/1.8/webrick/server.rb:82:in `start' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:293:in `start' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:144:in `newthread' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:143:in `initialize' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:143:in `new' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:143:in `newthread' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:291:in `start' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:290:in `each' /usr/lib64/ruby/site_ruby/1.8/puppet.rb:290:in `start' /usr/bin/puppetmasterd:285 err: Rails is missing; cannot store configurations
Related issues
History
Updated by Evan Borgstrom over 2 years ago
Err, sorry. The trace from above was from Ruby 1.8.6. I noticed in /usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/core_ext/benchmark.rb that it redefined benchmark for ruby < 1.8.7 so I upgraded. The trace remained the same except that it no longer used benchmark from activesupport and instead used the ruby core.
Updated by Luke Kanies over 2 years ago
- Status changed from Unreviewed to Duplicate
We’re not modifying 0.24.x at this point to be compatible with newer versions of Rails. If someone really needs a solution to this, please either provide a patch or contact us privately.