cd0cc47a6a
![Swaminathan Vasudevan](/assets/img/avatar_default.png)
With DVR routers, if a port is associated with a FloatingIP, before it is used by a VM, the FloatingIP will be initially started at the Network Node SNAT Namespace, since the port is not bound to any host. Then when the port is attached to a VM, the port gets its host binding, and then the FloatingIP setup should be migrated to the Compute host and the original FloatingIP in the Network Node SNAT Namespace should be cleared. But the original FloatingIP setup in SNAT Namespace was not cleared by the agent. This patch addresses the issue. Change-Id: I55a16bcc0020087aa1abe76f5bc85cd64ccdaecd Closes-Bug: #1796491
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst
Description
Languages
Python
99.7%
Shell
0.3%