Description of problem: The page http://docs.puppetlabs.com/mcollective/reference/integration/activemq_ssl.html describes the possibility of using SSL as the transport mechanism. It lists stomp gem 1.2.2+ as a prerequisite. Indeed, if plugin.activemq.pool.1.ssl = true is enabled in /etc/mcollective/server.cfg on current OpenShift Enterprise 1.2, error activemq.rb:226:in `rescue in ssl_parameters' Failed to set full SSL verified mode: RuntimeError: Stomp gem >= 1.2.2 is needed is shown in /var/log/mcollective.log upon service mcollective restart on the node. Please rebase ruby193-rubygem-stomp to 1.2.2, ideally the latest greatest (1.2.11). Version-Release number of selected component (if applicable): ruby193-rubygem-stomp-1.1.8-1.el6op.noarch How reproducible: Deterministic. Steps to Reproduce: 1. Enable plugin.activemq.pool.1.ssl = true in /etc/mcollective/server.cfg 2. Run service mcollective restart Actual results: activemq.rb:226:in `rescue in ssl_parameters' Failed to set full SSL verified mode: RuntimeError: Stomp gem >= 1.2.2 is needed in /var/log/mcollective.log. Expected results: No error, and SSL can be used instead of plain STOMP (once bug 995492 is addressed). Additional info:
I have verified that taking the .src.rpm of ruby193-rubygem-stomp-1.1.8-1.el6op.noarch and just replacing the Version value with 1.2.2 (and putting stomp-1.2.2.gem to SOURCES makes the .src.rpm and the .noarch.rpm build on RHEL 6. If you'd like to go with stomp-1.2.11.gem, line %{gem_instdir}/notes needs to be added to %files doc.
Verify this bug on puddle 1.2/2013-09-05.1. After the installation of broker and node, check the version of ruby193-rubygem-stomp package: [root@broker ~]# rpm -qa|grep rubygem-stomp ruby193-rubygem-stomp-1.2.2-1.el6op.noarch [root@node1 ~]# rpm -qa|grep rubygem-stomp ruby193-rubygem-stomp-1.2.2-1.el6op.noarch Enable activemq SSL, activemq and mcollective service both could start well, and no error logs. Broker could connect to node, and application could be created successfully. [root@broker ~]# mco ping node1.osetestv2auto.com time=100.14 ms
Based on https://bugzilla.redhat.com/show_bug.cgi?id=995492#c10 I decided to upgrade to the latest stomp version available. Would you mind sanity checking one more time?
Verify this bug with ruby193-rubygem-stomp-1.2.14-1.el6op.noarch on puddle 1.2/2013-09-06.1 After the installation of broker and node, check the version of ruby193-rubygem-stomp package: [root@broker ~]# rpm -qa|grep rubygem-stomp ruby193-rubygem-stomp-1.2.14-1.el6op.noarch [root@node1 ~]# rpm -qa|grep rubygem-stomp ruby193-rubygem-stomp-1.2.14-1.el6op.noarch Then enable activemq SSL, the activemq and mcollective service both could start well. Broker could connect to node, and application could be created successfully.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1275.html