Issue #7166 has been updated by Daniel Pittman.
So, to be clear: I worked to get this into 2.7.x because it was targetted Statler. So, it was no accident; the change itself seemed reasonable, contained, safe, and appropriate for this branch. I am surprised we decided to pull it, frankly. I thought the only question was if we intended another 2.6 request, or we just told people to apply the patch by hand down there and all. :) Meanwhile, we merged this to 2.6, and 2.7.1, but not 2.7.0? O_o ---------------------------------------- Bug #7166: Using storeconfigs with stomp server fills logs with warnings. https://projects.puppetlabs.com/issues/7166 Author: Jason Smith Status: Available In Testing Branch Priority: Normal Assignee: Jason Smith Category: stored configuration Target version: Statler Affected Puppet version: 2.6.7 Keywords: Branch: https://github.com/jamtur01/puppet/tree/tickets/master/7166 Our puppet server is configured using apache with Fusion Passenger and we recently enabled storeconfigs using stomp and activemq. It appears that puppet is using an old deprecated call to send in ruby's stomp library since our apache logs are filled with these warnings: This method is deprecated and will be removed on the next release. Use 'publish' instead which appears to come from the rubygem stomp module, see line 264 of: http://gitorious.org/stomp/mainline/blobs/master/lib/stomp/connection.rb -- 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.
