yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1230330

Title:
  ML2 plugin and drivers do not delete dhcp port upon deletion of
  network

Status in OpenStack Neutron (virtual network service):
  Fix Released

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_port_precommit(), create_port_postcommit().
    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_port_precommit() and delete_port_postcommit()
    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_port_pre/postcommit  call  dhcp port is never invoked. Hence, one will end up with a port with a vlan configured on it. 

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1230330/+subscriptions