Bug 1021536
| Summary: | Setting Qpid SSL protocol sets wrong variable | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Xavier Queralt <xqueralt> | |
| Component: | openstack-cinder | Assignee: | Eric Harney <eharney> | |
| Status: | CLOSED ERRATA | QA Contact: | Haim <hateya> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.0 | CC: | abaron, apevec, bperkins, dallan, ddomingo, dron, eharney, hateya, jruzicka, ndipanov, rcritten, sclewis, xqueralt, yeylon | |
| Target Milestone: | rc | Keywords: | TestOnly | |
| Target Release: | 4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | 996766 | |||
| : | 1045057 (view as bug list) | Environment: | ||
| Last Closed: | 2013-12-20 00:30:12 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, 1021537 | |||
| Bug Blocks: | 1055616 | |||
|
Comment 3
Eric Harney
2013-12-04 20:27:00 UTC
Will leave in POST since not ACK'd. 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 |