45ae9dfb7d
For now while updating FIP check if port or logical_ip has changed and only then we deleted the NAT entry. Unfortunately each time when FIP update occurs the method _create_or_update_floatingip() is used. It first deletes LSP pointed by FIP and adds it again along with new NAT entries. Based on author comment this actions are required. So if we don't update FIP with logical_ip or new port_id, like update a description, the NAT entries gets duplicated. Since all is wrapped withing a transaction and to not wait for proper fix (this code need sa refactor based on commments with NAT external_id column) I think thats safe just to delete the NAT entry in such situation like described above. Change-Id: Iea532e2a02b7992305d1b90aa040e064901c340c Related-Bug: #1859977
OpenStack Neutron
Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).
To learn more about neutron:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/neutron
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute, please read the CONTRIBUTING.rst file.