yahoo-eng-team team mailing list archive

[Chuck Short <chuck.short@xxxxxxxxxxxxx>]

** Changed in: neutron/juno
       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/1377156

Title:
  fg- device is not deleted after the deletion of the last VM on the
  compute node

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

Bug description:
  The external gateway port in the fip- namespace on a compute node is
  not removed after the user deleted the last VM running on the node.

  How to reproduce the problem:

  1. SETUP:
       * Use devstack to start up the controller node.  In local.conf, Q_DVR_MODE=dvr_snat.
       * Use devstack to setup a compute node.  In local.conf, Q_DVR_MODE=dvr.

  At the start, there are no VMs hosted on the compute node.  The fip
  namespace hasn't been created yet.

  1. Create a network and subnet
  2. Create a router and dd the subnet to the router
  3. Tie the router to the external network
  4. Boot up a VM using the network, and assign it a floatingip
  5. Ping the floating IP (make sure you open up your SG)
  6. Note the fg- device in the fip namespace on the compute node
  7. Now delete the VM

  Expected results:

  - The VM is deleted.
  - Neutron port-list shows the gateway port is also deleted.
  - The FIP namespace is also cleared

  Experienced results:

  - The fg- device still remains in the fip namespace on the compute
  node and the fip namespace isn't removed.

  For detailed command sequence, see:

  http://paste.openstack.org/show/118174/

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