fix quantum manager get_port_by_attachment
Bug #927507 reported by
dan wendlandt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
dan wendlandt | ||
neutron |
Fix Released
|
High
|
dan wendlandt |
Bug Description
there are two things wrong with this call:
1) quantum manager iterates through all ports on a quantum network when dellocating an instance in order to find out what port a particular vif is attached to. This should be updated to use the filtering capabilities of quantum, in which case only a single port will be returned.
2) this call need to be updated to handle the case where the network does not exist, since at the type of running the query, we do not know if the network in question belongs to the VM-owning tenant or the default tenant.
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → dan wendlandt (danwent) |
Changed in quantum: | |
status: | New → Fix Committed |
assignee: | nobody → dan wendlandt (danwent) |
milestone: | none → essex-4 |
importance: | Undecided → High |
Changed in nova: | |
milestone: | none → essex-4 |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
Changed in quantum: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/3796
Review: https:/