Bug 1021536 - Setting Qpid SSL protocol sets wrong variable
Summary: Setting Qpid SSL protocol sets wrong variable
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 4.0
Assignee: Eric Harney
QA Contact: Haim
Depends On: 996766 1021537
Blocks: 1055616
TreeView+ depends on / blocked
Reported: 2013-10-21 13:20 UTC by Xavier Queralt
Modified: 2019-09-09 16:50 UTC (History)
14 users (show)

Fixed In Version: openstack-cinder-2013.2-5.el6ost
Doc Type: Bug Fix
Doc Text:
By default, QPID uses TCP as a connection transport instead of connection protocol. Previously, the procedure for enabling SSL in QPID connections was to set 'qpid_protocol = ssl' in /etc/glance/glance-api.conf. This setting, however, sets connection protocol; the python-qpid client, on the other hand, expects a connection transport type. The mismatch prevented QPID from actually establishing an SSL connection. With this release, the 'qpid_protocol = ssl' setting now enables SSL for the connection transport instead of connection protocol. As such, QPID can now successfully establish SSL connections.
Clone Of: 996766
: 1045057 (view as bug list)
Last Closed: 2013-12-20 00:30:12 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1158807 0 None None None Never
OpenStack gerrit 47574 0 None None None Never
OpenStack gerrit 56993 0 None None None Never
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Comment 3 Eric Harney 2013-12-04 20:27:00 UTC
This is fixed in Cinder 2013.2 / RHOS 4.

- a7d47c4 Update to latest copy of OSLO incubator

Comment 4 Eric Harney 2013-12-04 20:28:12 UTC
Will leave in POST since not ACK'd.

Comment 15 errata-xmlrpc 2013-12-20 00:30:12 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.


Note You need to log in before you can comment on or make changes to this bug.