Bug 1055616

Summary: Setting Qpid SSL protocol sets wrong variable
Product: Red Hat OpenStack Reporter: Lon Hohberger <lhh>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: apevec, bperkins, breeler, dnavale, dron, eharney, jruzicka, mlopes, ndipanov, nlevinki, rcritten, sclewis, xqueralt, yeylon
Target Milestone: z3Keywords: TestOnly, ZStream
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
URL: https://code.engineering.redhat.com/gerrit/gitweb?p=cinder.git;a=blob;f=cinder/openstack/common/rpc/impl_qpid.py;h=8f18ae0b48374958224a7f5f7f48c60116b7dd99;hb=034fa31a8c9b2a34faaab0de6ee8fe74264a5005#l427
Whiteboard:
Fixed In Version: openstack-cinder-2013.2.1-1.el6ost Doc Type: Bug Fix
Doc Text:
In the Openstack Block Storage service, there was an issue in setting qpid_protocol to ssl in the cinder.conf file in order to enable SSL. This resulted in the SSL not being enabled. With this bug fix, the correct variable is now set in the connection code to signal that SSL should be used. As a result, the SSL protocol is used in QPid when requested.
Story Points: ---
Clone Of: 1045057 Environment:
Last Closed: 2014-03-25 19:23:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 996766, 1021536, 1021537    
Bug Blocks:    

Comment 2 Lon Hohberger 2014-01-20 15:53:38 UTC
*** Bug 1045057 has been marked as a duplicate of this bug. ***

Comment 3 Eric Harney 2014-01-21 16:08:58 UTC
Already in RHOS4 as this was in upstream 2013.2.

Comment 5 nlevinki 2014-03-19 07:21:15 UTC
We run sanity sutomation to verify the fix doesn't break the system and it is working correctly.
We found an issue with glance - packstack installation doesn't configure glance config file correctly regarding qpid ssl enable.
we will open a different ticket for this issue.

Comment 7 errata-xmlrpc 2014-03-25 19:23:27 UTC
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-2014-0334.html