Always send status update for processed floating ips
Currently l3 agent skips status update for floating ips in case
status didn't change: this might be wrong if status has changed
on server side while agent was processing. See bug for details.
L3 agent skips floating ip processing in case ip address exists
on external device. So we can still skip status update for such
floating ips.
Closes-Bug: #1505557
Conflicts:
neutron/tests/unit/agent/l3/test_agent.py
Change-Id: I908fe5a0555f68ab85e7d199c36a903b915e103f
(cherry picked from commit 7592b17b8793c0e296c77bd17929f3db37f1483e)
Reviewed: https:/ /review. openstack. org/235855 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=0a0b5c452b1 5952877493abd85 387e3c4eef8872
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 0a0b5c452b15952 877493abd85387e 3c4eef8872
Author: Oleg Bondarev <email address hidden>
Date: Tue Oct 13 11:55:02 2015 +0300
Always send status update for processed floating ips
Currently l3 agent skips status update for floating ips in case
status didn't change: this might be wrong if status has changed
on server side while agent was processing. See bug for details.
L3 agent skips floating ip processing in case ip address exists
on external device. So we can still skip status update for such
floating ips.
Closes-Bug: #1505557
Conflicts:
neutron/ tests/unit/ agent/l3/ test_agent. py
Change-Id: I908fe5a0555f68 ab85e7d199c36a9 03b915e103f 296c77bd17929f3 db37f1483e)
(cherry picked from commit 7592b17b8793c0e