ML2 plugin and drivers do not delete dhcp port upon deletion of network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Robert Kukura |
Bug Description
When all VM instances on a given network are deleted, followed by deletion of the network, the dhcp port is not deleted.
Here are steps to reproduce this bug:
- Create a network.
- Launch a VM
- ML2 driver gets a call to create_
This is called twice - once with device-id of Instance (VM) - compute:none
Second time the same calls are invoked - with device-id network:dhcp
- Delete the VM
- ML2 driver gets a call to delete_
This only gets called once with device-id of Instance (VM) - compute:none
There is no delete port call for dhcp - this makes sense, as the network still exists.
- Delete the network as well.
- Now at this point, no network, no VMs
delete_
During this exercise, I examine the neutron ports DB. I notice that both ports (dhcp as well port connecting to instance) are created and deleted from the DB as expected. So, this means that things north of ML2 plugin seem to be OK.
-Sukhdev
Changed in neutron: | |
assignee: | nobody → Sukhdev Kapur (sukhdev-8) |
Changed in neutron: | |
milestone: | none → havana-rc1 |
importance: | Undecided → High |
Changed in neutron: | |
assignee: | Sukhdev Kapur (sukhdev-8) → Robert Kukura (rkukura) |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | havana-rc1 → 2013.2 |
Fix proposed to branch: master /review. openstack. org/48546
Review: https:/