legacy_net_info guard incompatible with new-style NetworkInfo
Bug #1164152 reported by
Rick Harris
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Rick Harris | ||
Grizzly |
Fix Released
|
Low
|
Unassigned |
Bug Description
In order to fix https:/
a guard was added to _init_instance in compute manger.
The problem is that the guard assumed that `legacy_net_info` would always be a tuple which is not true. Depending on the config, it may be a list of tuples, or a NetworkInfo object.
Changed in nova: | |
assignee: | nobody → Rick Harris (rconradharris) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
tags: | added: vmware-co-preferred |
tags: |
added: vmware removed: vmware-co-preferred |
Changed in openstack-vmwareapi-team: | |
status: | New → Fix Released |
Changed in openstack-vmwareapi-team: | |
importance: | Undecided → Low |
no longer affects: | openstack-vmwareapi-team |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/26042
Review: https:/