yahoo-eng-team team mailing list archive

[Swaminathan Vasudevan <swaminathan.vasudevan@xxxxxx>]

Public bug reported:

When a VM with FloatingIP is deleted without disassociating a FIP, the
internal FIP agent gateway port on that particular compute node is not
deleted.

1. Create a dvr router.
2. Attach a subnet to the router
3. Attach a Gateway to the router
4. Create a Floating IP
5. Create a VM on the above subnet
6. Associate the Floating IP to the VM's private IP.
7. Now do a port-list you will see a port with device_owner as "router:floatingip_agent_gw"
8. Delete the VM ( nova delete VM-name).
9. The port still remains.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-dvr-backlog

** Tags added: l3-dvr-backlog

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

Title:
  When a VM with FloatingIP is directly deleted without disassociating a
  FIP, the fip agent gateway port is not deleted.

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When a VM with FloatingIP is deleted without disassociating a FIP, the
  internal FIP agent gateway port on that particular compute node is not
  deleted.

  1. Create a dvr router.
  2. Attach a subnet to the router
  3. Attach a Gateway to the router
  4. Create a Floating IP
  5. Create a VM on the above subnet
  6. Associate the Floating IP to the VM's private IP.
  7. Now do a port-list you will see a port with device_owner as "router:floatingip_agent_gw"
  8. Delete the VM ( nova delete VM-name).
  9. The port still remains.

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