floatingip_agent_gateway port is not deleted on fip disassociate

[Mike Smith]

When the last FIP is disassociated on a node, the floating IP agent gateway port should be deleted from the db. The same thing should happen when a nova VM is deleted on a host which was the last FIP associated VM. The delete VM path is currently working, but the disassociate path is not.

[Haifeng.Yan (yanheven)]

" floating IP agent gateway port"?

[Swaminathan Vasudevan (swaminathan-vasudevan)]

hi sridhar gaddam, I have found a fix for this issue, but if you are work is in progress I will review it, otherwise I will take it up.

[Sridhar Gaddam (sridhargaddam)]

Hello Swaminathan,

I was planning to look into this issue today. Since you already have the fix, please go ahead and propose the patch. Thanks.

--Sridhar.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/137247

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/137247
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1d80f54fb9c0642489a9fa9f922406e1fdd58b6e
Submitter: Jenkins
Branch: master

commit 1d80f54fb9c0642489a9fa9f922406e1fdd58b6e
Author: Swaminathan Vasudevan <email address hidden>
Date: Tue Nov 25 15:47:59 2014 -0800

    Deletes floating agent gw port on disassociate

    This patch deletes the floating agent gw port
    on floatingip disassociate.

    A recent change in the neutron trunk broke
    this functionality. This was introduced by
    the patch that addressed the re-order
    operations in (l3_dvr) update floating ip.

    The current patch fixes the problem.

    Change-Id: I98e766cf4ed33412d9d5dae07217553acbb5009c
    Closes-Bug: #1394026