Disabling an ML2 type driver can leave orphaned DB records
Bug #1311470 reported by
Kevin Benton
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Medium
|
Unassigned |
Bug Description
If an ML2 type driver is disabled after segments have been allocated using that type driver, subsequent network deletions will not remove the DB records allocated by that type driver since the driver isn't there to release the segment[1]. These orphaned segments will then be unavailable for use if the type driver is re-enabled later.
tags: | added: ml2 |
Changed in neutron: | |
importance: | Undecided → Low |
status: | New → Confirmed |
importance: | Low → Medium |
Changed in neutron: | |
status: | Confirmed → Incomplete |
Changed in neutron: | |
assignee: | nobody → navin (navinchandra-salunke) |
Changed in neutron: | |
milestone: | none → kilo-1 |
Changed in neutron: | |
milestone: | kilo-1 → kilo-2 |
Changed in neutron: | |
milestone: | kilo-2 → kilo-3 |
Changed in neutron: | |
milestone: | kilo-3 → kilo-rc1 |
Changed in neutron: | |
assignee: | nobody → Sreekumar S (sreesiv) |
Changed in neutron: | |
status: | In Progress → Incomplete |
assignee: | Sreekumar S (sreesiv) → nobody |
To post a comment you must log in.
I was just going through this bug.
On Openstack website, in ML2 description, Following warning has been given:
"Disabling a ML2 type driver and re-enabling it later may lead to database inconsistencies if ML2 is reconfigured without support for that type. "
see: docs.openstack. org/admin- guide-cloud/ content/ ml2_scenarios. html
http://
We can solve this with some work around. But before jump to find out solution I want to know your view.