Native L3 plugin is not deleting the NAT entry when the port associated with a floating ip is deleted

[Numan Siddique]

Steps to reproduce

1. neutron floatingip-create public
2. neutron port-create private
3. neutron floatingip-associate FIP_ID PORT_ID
4. neutron port-delete PORT_ID

After the step 4, the row in the NAT table of NB DB is not deleted.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/399592
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=52b29eabeee895c6d921e8e965c1bfe539f22bf6
Submitter: Jenkins
Branch: master

commit 52b29eabeee895c6d921e8e965c1bfe539f22bf6
Author: Numan Siddique <email address hidden>
Date: Fri Nov 18 18:23:46 2016 +0530

    Update GW SNAT rule in if already exists for 'dnat_and_snat' type

    When a floating ip is associated to a fixed ip, a row in NAT table
    is created for the gateway router. When the port with the fixed ip
    is deleted without disassociating the fip, the row still remains.
    When the same floating ip is associated to a different fixed ip,
    a new row is created in the NAT table. This causes the floating ip
    unreachable.

    In this patch, we first check for the presence of the NAT rule
    for the floating ip and if present update the same to the new
    fixed ip value.

    Change-Id: Id36436032a37e0ae4c6ae9a23b1de5bf4da5b3fd
    Closes-bug: #1642898

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-ovn 2.0.0.0b2 development milestone.