Bug 1040162
Summary: | Qpid protocol configuration is wrong, affects SSL | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Rob Crittenden <rcritten> |
Component: | openstack-glance | Assignee: | Flavio Percoco <fpercoco> |
Status: | CLOSED ERRATA | QA Contact: | Haim <hateya> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.0 | CC: | apevec, ddomingo, dron, eglynn, fpercoco, hateya, yeylon |
Target Milestone: | rc | Keywords: | OtherQA |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-glance-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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-20 00:44:03 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: | |||
Bug Blocks: | 998599 |
Description
Rob Crittenden
2013-12-10 20:59:51 UTC
This is a one-line change fixed post-havana GA. This was already merged upstream. Looks like it didn't get in during the last build. The upstream fix: https://github.com/openstack/glance/commit/e20b2af381629d1f3923647952679871a68126f3 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/RHEA-2013-1859.html |