Description of problem: During authentication of RHOS credentials, get the failure notice Version-Release number of selected component (if applicable): 5.4.0.0.24.20150427192818_1fd9e49 How reproducible: Uncertain Steps to Reproduce: 1. Define RHOS6 Cloud Provider 2. Provide Credentials 3. Actual results: "MIQ(OpenstackQpidConnection).available?) Failed to load qpid_messaging gem. Qpid AMQP messaging will not be available. Enable debug logging to see the associated exception." Expected results: No message, appropriate messaging gem loaded Additional info:
This is likely a blocker bug, based on a quick look at an appliance: > # rpm -qa | grep cfme > cfme-lib-5.4.0.0.24-1.el6cf.x86_64 > cfme-gemset-5.4.0.0.24-1.el6cf.x86_64 > cfme-5.4.0.0.24-1.el6cf.x86_64 > cfme-appliance-5.4.0.0.24-1.el6cf.x86_64 > # rpm -qa | grep qpid > ruby200-rubygem-qpid_messaging-0.20.2-5.el6cf.x86_64 > qpid-cpp-client-ssl-0.14-22.el6_3.x86_64 > qpid-cpp-client-0.14-22.el6_3.x86_64 > [vmdb]# cat .bundle/config > --- > BUNDLE_JOBS: 3 > BUNDLE_WITHOUT: test:development:metric_fu:qpid We can't bundle without qpid for appliances
Thom, Can you please try something for me? On the appliance patch the .bundle/config file with the following command" sed -i "s/:qpid//g" /var/www/miq/vmdb/.bundle/config Then confirm if things work as expected. Thank you! JoeV
As noted while working together w/Thom the sed/edit followed by a evm restart is a workaround for the current build. A permanent fix will show up in the next build.
This will make it into the next 5.4 build 5.4.0.0.26
Just FYI - I did a simple confirmation test to ensure this is fixed in the 5.4.0.0.26 image. I booted and configured the vsphere then did: # vmdb # bundle exec rails c irb(main):001:0> require 'qpid_messaging' => true JoeV
Verified in 5.4.0.0.26.20150511144816_f924bd4 (per Comment 9)
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. https://rhn.redhat.com/errata/RHBA-2015-1100.html