Issue #2840 has been updated by James Turnbull.

Target version changed from Puppet - 0.25.4 to Puppet - 0.25.5


----------------------------------------
Bug #2840: Backwards incompatibility with 0.24.7 against 0.25.1 + passenger
http://projects.reductivelabs.com/issues/2840

Author: Pete Emerson
Status: Needs more information
Priority: Normal
Assigned to: Christian Hofstaedtler
Category: passenger
Target version: 0.25.5
Affected version: 0.25.1
Keywords: 
Branch: 


According to http://reductivelabs.com/trac/puppet/wiki/ReleaseNotes it seems 
that I should be able to use an older client with my new 0.25.1 puppetmaster, 
but I am unable to get a 0.24.7 client working with a 0.25.1 puppetmaster. In 
fact, it appears to be crashing the puppetmaster when I try. I think it's 
passenger related because when I switch back to webrick the problem goes away.

Puppetmaster:

CentOS release 5.4
ruby 1.8.5 (2006-08-25) [x86_64-linux]
puppet-server-0.25.1-0.2.rc2.el5
puppet-0.25.1-0.2.rc2.el5
fastthread (1.0.7)
passenger (2.2.5)
rack (1.0.1)
rake (0.8.7)
Patch applied: http://groups.google.com/group/puppet-dev/msg/b15e1c93bbc70fdb

Puppet node:

puppet-0.24.7-4.el5

The puppet node:

<pre>
err: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP-Error: 500 
Internal Server Error>
err: Could not retrieve catalog: HTTP-Error: 500 Internal Server Error
</pre>

The puppetmaster logs:

<pre>
Backtrace:
Puppet Server (Rack): Internal Server Error: Unhandled Exception: "undefined 
method `ssl_client_header'
for #<Puppet::Network::HTTP::RackXMLRPC:0x2aaaac248c50>"
 > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack/xmlrpc.rb:48:in 
 > `build_client_request'
 > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack/xmlrpc.rb:33:in 
 > `process'
 > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack.rb:48:in `call'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/request_handler.rb:95:in
`process_request'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_request_handler.rb:207:in
`main_loop'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:118:in
`run'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:69:in
`spawn_application'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/utils.rb:183:in
 >  `safe_fork'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:62:in
`spawn_application'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/rack/application_spawner.rb:45:in
`spawn_application'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:159:in
`spawn_application'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/spawn_manager.rb:287:in
`handle_spawn_application'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
 >  `__send__'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:352:in
 >  `main_loop'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
 > /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server:61
</pre>

Also, if I pull the patch applied out, it does not solve the problem.



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

Reply via email to