With the current change in allowing the unbound fip
to be associated with the snat node, we are seeing
that all floating IPs that are associated with an
unbound port are created at the snat node.
This is also applicable for floating IPs that are
created just before associating the port to a VM.
We have seen such scenarios in the test cases.
This is the right behavior as per design. But when
the port is bound to a host, the floating IP should
be migrated to the respective host.
This patch fixes the issue by sending notification to
the respective node, when the port is bound and also
clear the fip from the snat node.
Closes-Bug: #1718788
Change-Id: I6b1f3ffc3c3336035632f6a82d3a87b3be57b403
(cherry picked from commit 27fcf86bcbf4a66f52385f0efea956f13c38d7b2)
Reviewed: https:/ /review. openstack. org/513816 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=c3f395db670 5c1054a16fc0f73 0f59446a4229f8
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit c3f395db6705c10 54a16fc0f730f59 446a4229f8
Author: Swaminathan Vasudevan <email address hidden>
Date: Tue Sep 19 06:54:14 2017 -0700
DVR: Fix unbound fip port migration to bound port
With the current change in allowing the unbound fip
to be associated with the snat node, we are seeing
that all floating IPs that are associated with an
unbound port are created at the snat node.
This is also applicable for floating IPs that are
created just before associating the port to a VM.
We have seen such scenarios in the test cases.
This is the right behavior as per design. But when
the port is bound to a host, the floating IP should
be migrated to the respective host.
This patch fixes the issue by sending notification to
the respective node, when the port is bound and also
clear the fip from the snat node.
Closes-Bug: #1718788 035632f6a82d3a8 7b3be57b403 f52385f0efea956 f13c38d7b2)
Change-Id: I6b1f3ffc3c3336
(cherry picked from commit 27fcf86bcbf4a66