quantum network manager doesn't accept instance_uuid as a keyword arg
Bug #914962 reported by
Matt Dietz
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Trey Morris | ||
neutron |
Fix Released
|
Critical
|
Trey Morris |
Bug Description
See http://
The quantum network manager needs to be updated to accept instance_uuid as an argument. This is clearly preventing deletes from finishing using nova, quantum and melange
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in quantum: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → essex-3 |
Changed in quantum: | |
importance: | High → Critical |
Changed in quantum: | |
assignee: | nobody → Isaku Yamahata (yamahata) |
Changed in quantum: | |
assignee: | Isaku Yamahata (yamahata) → nobody |
assignee: | nobody → Trey Morris (tr3buchet) |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → essex-3 |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-3 → 2012.1 |
Changed in quantum: | |
milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
I ran into this as well. Do we know what changes broke this? Fixing this is probably pretty easy, but we should also be sure to add a unit test to improve coverage.