[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/661011 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=946faaf3610 03a0a67081be285 65d3815c354510
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 946faaf361003a0 a67081be28565d3 815c354510
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