DVR: handle floating IP reassociation on the same host
The case when floating IP is reassociated from one VM to another
on the same host without doing disassociation, was not properly handled:
l3 dvr agent only checked that the floating address was present on the
device in router namespace and considered floating IP confiigured correctly.
This patch adds fip_mapping to router object so fixed IP change can be
detected and handled.
Closes-Bug: #1599089
(cherry picked from commit b8a2cb813225ae6178f34363cab9a2446d471472)
Reviewed: https:/ /review. openstack. org/341848 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=1b9168be872 d4f17236ef085a7 0cf2d152c5a217
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit 1b9168be872d4f1 7236ef085a70cf2 d152c5a217
Author: Oleg Bondarev <email address hidden>
Date: Tue Jul 5 12:15:03 2016 +0300
DVR: handle floating IP reassociation on the same host
The case when floating IP is reassociated from one VM to another
on the same host without doing disassociation, was not properly handled:
l3 dvr agent only checked that the floating address was present on the
device in router namespace and considered floating IP confiigured correctly.
This patch adds fip_mapping to router object so fixed IP change can be
detected and handled.
Closes-Bug: #1599089 178f34363cab9a2 446d471472)
(cherry picked from commit b8a2cb813225ae6
Conflicts: tests/functiona l/agent/ l3/test_ dvr_router. py 9b90f225f374171 42e2304deb8
neutron/
Change-Id: I25c23bb9ad7b9a