QuantumManager does not initiate unplug on the linux_net driver
Bug #922356 reported by
Sumit Naiksatam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Sumit Naiksatam | ||
neutron |
Fix Released
|
High
|
Sumit Naiksatam |
Bug Description
QuantumManager does not initiate the call to unplug on the linux_net driver resulting in gateway devices of deleted networks being orphaned. Over a period of time this results in several unwanted devices, and it's difficult to keep track of which devices are valid and which are invalid. Manual deletion has to be performed on each device, clearly not an acceptable option in a production environment.
Changed in quantum: | |
assignee: | nobody → Brad Hall (bgh) |
Changed in quantum: | |
assignee: | Brad Hall (bgh) → nobody |
Changed in quantum: | |
assignee: | nobody → Sumit Naiksatam (snaiksat) |
Changed in quantum: | |
milestone: | essex-4 → none |
Changed in quantum: | |
milestone: | none → essex-rc1 |
Changed in quantum: | |
status: | New → In Progress |
tags: | added: low-hanging-fruit |
summary: |
- QuantumManager does not invoke unplug on the linux_net driver + QuantumManager does not initiate unplug on the linux_net driver |
Changed in quantum: | |
importance: | Medium → High |
description: | updated |
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → Sumit Naiksatam (snaiksat) |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | none → essex-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
Changed in quantum: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/5191
Review: https:/