On Ubuntu 12.04, after upgrading libapache2-mod-passenger from 2.2.11debian-2 to 2.2.11debian-2+deb6u1ubuntu12.04.1, puppet fails with :
Warning: Error 500 on SERVER: {"issue_kind":"RUNTIME_ERROR","message":"Server Error: undefined method `upcase' for nil:NilClass","stacktrace":["/usr/lib/ruby/vendor_ruby/puppet/network/http/route.rb:80:in `process'","/usr/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:63:in `process'","/usr/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile'","/usr/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile'","/usr/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:61:in `process'","/usr/lib/ruby/vendor_ruby/puppet/network/http/rack.rb:21:in `call'","/usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:92:in `process_request'","/usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'","/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:118:in `run'","/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:65:in `spawn_application'","/usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:in `safe_fork'","/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:58:in `spawn_application'","/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:41:in `spawn_application'","/usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:159:in `spawn_application'","/usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'","/usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__'","/usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop'","/usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously'","/usr/lib/phusion_passenger/passenger-spawn-server:61"]}
This seems to be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812103
Quoting from that bug :
« It is a regression, there's no way for applications using
mod_passenger to work after the latest update. Not only did the update
switch to a native package and drop some documentation, but it broke
the module.
Granted, the package is safer now that it doesn't work. »
Status changed to 'Confirmed' because the bug affects multiple users.