But it also changed the behavior to not enable IPv4
metadata in this case. Restore the old behavior by
not returning early in the DAD failure case. The callback
that builds the config file was moved until after
the address was bound to make the two steps more obvious.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/885270 /opendev. org/openstack/ neutron/ commit/ 1a711f399abebff 6572551ef4e3f7b 92397caab5
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/zed
commit 1a711f399abebff 6572551ef4e3f7b 92397caab5
Author: Brian Haley <email address hidden>
Date: Mon May 15 12:29:42 2023 -0400
Start metadata proxy even if IPv6 DAD fails
A recent change suppressed the IPv6 DAD failure and /review. opendev. org/c/openstack /neutron/ +/880957
removed the address when multiple DHCP agents were
configured on the same network,
https:/
But it also changed the behavior to not enable IPv4
metadata in this case. Restore the old behavior by
not returning early in the DAD failure case. The callback
that builds the config file was moved until after
the address was bound to make the two steps more obvious.
Conflicts:
neutron/ tests/unit/ agent/metadata/ test_driver. py
Related-bug: #1953165 33ca27ff7312f5b 2c7ea41e94f e6ffb3628ef1feb 12a62a9cfa) 15582b80d1909e3 565d859e9b)
Change-Id: I8436c6c9da9a25
(cherry picked from commit 846003c4379124d
(cherry picked from commit e7f85abae6a46a1