Issue #9158 has been updated by Digant Kasundra.
I added the patch to your 2.7.3 package and I get the following error. /usr/lib/ruby/1.8/puppet/indirector/rest.rb:56:in `deserialize' /usr/lib/ruby/1.8/puppet/indirector/rest.rb:120:in `find' /usr/lib/ruby/1.8/puppet/indirector/indirection.rb:188:in `find' /usr/lib/ruby/1.8/puppet/configurer.rb:240:in `retrieve_new_catalog' /usr/lib/ruby/1.8/puppet/util.rb:429:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/1.8/puppet/util.rb:428:in `thinmark' /usr/lib/ruby/1.8/puppet/configurer.rb:239:in `retrieve_new_catalog' /usr/lib/ruby/1.8/puppet/configurer.rb:86:in `retrieve_catalog' /usr/lib/ruby/1.8/puppet/configurer.rb:111:in `retrieve_and_apply_catalog' /usr/lib/ruby/1.8/puppet/configurer.rb:150:in `run' /usr/lib/ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock' /usr/lib/ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/1.8/puppet/agent.rb:103:in `with_client' /usr/lib/ruby/1.8/puppet/agent.rb:37:in `run' /usr/lib/ruby/1.8/puppet/application.rb:172:in `call' /usr/lib/ruby/1.8/puppet/application.rb:172:in `controlled_run' /usr/lib/ruby/1.8/puppet/agent.rb:35:in `run' /usr/lib/ruby/1.8/puppet/application/agent.rb:336:in `onetime' /usr/lib/ruby/1.8/puppet/application/agent.rb:310:in `run_command' /usr/lib/ruby/1.8/puppet/application.rb:307:in `run' /usr/lib/ruby/1.8/puppet/application.rb:411:in `hook' /usr/lib/ruby/1.8/puppet/application.rb:307:in `run' /usr/lib/ruby/1.8/puppet/application.rb:402:in `exit_on_fail' /usr/lib/ruby/1.8/puppet/application.rb:307:in `run' /usr/lib/ruby/1.8/puppet/util/command_line.rb:69:in `execute' /usr/bin/puppet:4 err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not write jimhenson1.stanford.edu to queue: wrong number of arguments (4 for 3) Instance::#<Puppet::Resource::Catalog:0xb5500e14> client : #<Puppet::Util::Queue::Stomp:0xb64abbac> warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run ---------------------------------------- Bug #9158: Puppet master breaks on trying to send message to stomp queue https://projects.puppetlabs.com/issues/9158 Author: Digant Kasundra Status: In Topic Branch Pending Review Priority: Normal Assignee: Daniel Pittman Category: queuing Target version: 2.6.x Affected Puppet version: 2.7.1 Keywords: Branch: When a client checks in to the puppetmaster, the puppet master attempts to send a message to the stomp queue (if async stored configs is on) and in doing so attempts to use a method that doesn't exist. This effectively completely breaks puppet in 2.7.1 for us. The following patch will fix this: --- stomp.rb.orig 2011-08-22 17:30:16.000000000 -0700 +++ stomp.rb 2011-08-22 17:13:07.000000000 -0700 @@ -29,7 +29,7 @@ end def publish_message(target, msg) - stomp_client.publish(stompify_target(target), msg, :persistent => true) + stomp_client.send(stompify_target(target), msg, :persistent => true) end def subscribe(target) -- 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.
