[DHCP] Don't resync network if same port is alredy in cache
Sometimes when port is created on dhcp agent's side, it may happend
that same port is already in network cache.
Before this patch if port with same IP address was already in cache,
resync was rescheduled because of duplicate IPs found in cache.
Now resync will be scheduled only if duplicate IP address belongs to
port with different MAC address or different id.
Change-Id: I23afbc10725f5dc78e3c63e6e505ef89ba8dc4a5
Closes-Bug: #1824802
(cherry picked from commit 5c433a027daab2419d974820589205253871885e)
Reviewed: https:/ /review. opendev. org/661012 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=55055172958 bd278020d08cd80 d7f7641a3f7520
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 55055172958bd27 8020d08cd80d7f7 641a3f7520
Author: Slawek Kaplonski <email address hidden>
Date: Fri May 10 10:47:00 2019 +0200
[DHCP] Don't resync network if same port is alredy in cache
Sometimes when port is created on dhcp agent's side, it may happend
that same port is already in network cache.
Before this patch if port with same IP address was already in cache,
resync was rescheduled because of duplicate IPs found in cache.
Now resync will be scheduled only if duplicate IP address belongs to
port with different MAC address or different id.
Change-Id: I23afbc10725f5d c78e3c63e6e505e f89ba8dc4a5 19d974820589205 253871885e)
Closes-Bug: #1824802
(cherry picked from commit 5c433a027daab24