agent gateway port left behind when deleting VM with FIP
Bug #1367588 reported by
Swaminathan Vasudevan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Swaminathan Vasudevan |
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:
8. Delete the VM ( nova delete VM-name).
9. The port still remains.
tags: | added: l3-dvr-backlog |
Changed in neutron: | |
status: | New → Confirmed |
summary: |
- When a VM with FloatingIP is directly deleted without disassociating a - FIP, the fip agent gateway port is not deleted. + When the last VM with FloatingIP is directly deleted without + disassociating a FIP, the fip agent gateway port is not deleted on the + plugin side and the fip namespace on the Compute Node is not deleted by + the L3 Agent. |
Changed in neutron: | |
importance: | Undecided → Medium |
summary: |
- When the last VM with FloatingIP is directly deleted without - disassociating a FIP, the fip agent gateway port is not deleted on the - plugin side and the fip namespace on the Compute Node is not deleted by - the L3 Agent. + agent gateway port left behind when deleting VM with FIP |
Changed in neutron: | |
milestone: | none → juno-rc1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/120885
Review: https:/