Delete the rule in SNAT table (in NB DB) when the port associated with a floating ip is deleted

[Numan Siddique]

The review [1] addressing the bug [2] by updating the row in NAT table when the floating ip is re-associated to another port.

The rule in NAT table of type "dnat_and_snat" can be deleted when the port gets deleted if it has any floating ip association.

[1] - https://review.openstack.org/#/c/399592/
[2] - https://bugs.launchpad.net/networking-ovn/+bug/1642898

[Lucas Alvares Gomes (lucasagomes)]

Hi @Numan,

Can we have some steps about how to reproduce this problem ? (If it's easy enough)

[Numan Siddique (numansiddique)]

@Lucas - Hi. Sorry for not responding to this. The description in the bug - https://bugs.launchpad.net/networking-ovn/+bug/1642898 has steps.

[Reedip (reedip-banerjee-deactivatedaccount)]

Hi,
https://bugs.launchpad.net/networking-ovn/+bug/1642898 has been fixed. Should this be closed now ?

[Alan Rogger (alanrogger007)]

I have been facing the same bug in the DNAT so I tried to manage it somehow but literally, the browser started crashing which is the reason I checked https://errorcode0x.com/chrome-crashing-windows-10-solved/ for the solution of the problem.

[Reedip (reedip-banerjee-deactivatedaccount)]

Closing the bug since https://review.openstack.org/#/c/399592/ is removing the dnat_and_snat entry as well