Qpid SSL protocol
Bug #1158807 reported by
JuanFra Rodriguez Cardoso
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
Grizzly |
Fix Released
|
High
|
Unassigned | ||
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
Grizzly |
Fix Released
|
High
|
Unassigned | ||
neutron |
Invalid
|
Undecided
|
Unassigned | ||
Grizzly |
Fix Released
|
High
|
Unassigned | ||
oslo-incubator |
Fix Released
|
High
|
Davanum Srinivas (DIMS) |
Bug Description
By default, TCP is used as transport for QPID connections. If you like to enable SSL, there is a flat 'qpid_protocol = ssl' available in nova.conf. However, python-qpid client is awaiting transport type instead of protocol. It seems to be a bug:
Solution: (https:/
WRONG: self.connection
CORRECT: self.connection
Regards,
JuanFra.
affects: | nova → oslo |
affects: | oslo → nova |
affects: | nova → oslo |
Changed in oslo: | |
importance: | Undecided → High |
tags: | added: grizzly-backport-potential |
Changed in oslo: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in oslo: | |
milestone: | havana-1 → 2013.2 |
Changed in cinder: | |
status: | New → Invalid |
tags: | removed: grizzly-backport-potential in-stable-grizzly |
Changed in nova: | |
status: | New → Invalid |
Changed in neutron: | |
status: | New → Invalid |
To post a comment you must log in.
JuanFra,
Next time can you please follow steps here to contribute code changes? I'll take care of it this time :)
https:/ /wiki.openstack .org/wiki/ HowToContribute #If_you. 27re_a_ developer. 2C_start_ here
thanks,
dims