NVP connection fails because port is a string
Bug #1255519 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Salvatore Orlando | ||
Havana |
Fix Released
|
Medium
|
Salvatore Orlando |
Bug Description
On a dev machine I've recently create I noticed failures at startup when Neutron is configured with the NVP plugin.
I root caused the failure to port being explicitly passed to HTTPSConnection constructor as a string rather than an integer.
This can be easily fixed ensuring port is always an integer.
I am not sure of the severity of this bug as it might strictly related to this specific dev env, but it might be worth applying and backporting it
tags: |
added: nicira removed: nvp |
tags: | removed: grizzly-backport-potential |
Changed in neutron: | |
milestone: | icehouse-1 → icehouse-2 |
tags: | removed: havana-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/58751
Review: https:/