destroy_metadata_proxy not called from _destroy_router_namespaces
Bug #1252856 reported by
Carl Baldwin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Carl Baldwin | ||
Havana |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In preparing the patch for bug 1250596 I found that _destroy_
It may be that it was not called because _destroy_
Changed in neutron: | |
assignee: | nobody → Carl Baldwin (carl-baldwin) |
summary: |
- _spawn/destroy_metadata_proxy cannot be called from contexts where full - router_info is not available + destroy_metadata_proxy not called from _destroy_router_namespaces |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
milestone: | none → icehouse-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/57293 github. com/openstack/ neutron/ commit/ 07d597079781967 f5a149f1812ddca 3897fa49d9
Committed: http://
Submitter: Jenkins
Branch: master
commit 07d597079781967 f5a149f1812ddca 3897fa49d9
Author: Carl Baldwin <email address hidden>
Date: Tue Nov 19 17:47:43 2013 +0000
Call _destroy_ metadata_ proxy from _destroy_ router_ namespaces
Refactor _spawn/ destroy_ metadata_ proxy so that it can be called
with only the namespace and the router_id.
Change-Id: Id1c33b22c7c3bd 35c54a7c9ad4198 31bfed8746b
Closes-Bug: #1252856