OVN: Always try and create a metadata port on subnets
When a subnet is updated, for example, to disable then
re-enable DHCP on it, if there is no metadata port it
will just return without trying to allocate an IP,
leaving DHCP unusable on the subnet. This could happen
if an admin, even accidentally, deletes the DHCP port
on a subnet while DHCP is disabled.
This also makes OVN behave like ML2/OVS, which will
re-create the DHCP port when the enable_dhcp flag is
changed to false and back to true.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/883508 /opendev. org/openstack/ neutron/ commit/ 5b96edbeef8f76b 57be7bd5f93d8c0 acfc430a61
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/ussuri
commit 5b96edbeef8f76b 57be7bd5f93d8c0 acfc430a61
Author: Brian Haley <email address hidden>
Date: Fri Apr 7 17:06:40 2023 -0400
OVN: Always try and create a metadata port on subnets
When a subnet is updated, for example, to disable then
re-enable DHCP on it, if there is no metadata port it
will just return without trying to allocate an IP,
leaving DHCP unusable on the subnet. This could happen
if an admin, even accidentally, deletes the DHCP port
on a subnet while DHCP is disabled.
This also makes OVN behave like ML2/OVS, which will
re-create the DHCP port when the enable_dhcp flag is
changed to false and back to true.
Conflicts: plugins/ ml2/drivers/ ovn/mech_ driver/ ovsdb/ovn_ client. py plugins/ ml2/drivers/ ovn/mech_ driver/ ovsdb/ovn_ db_sync. py tests/unit/ plugins/ ml2/drivers/ ovn/mech_ driver/ test_mech_ driver. py
neutron/
neutron/
neutron/
Change-Id: I943f2fb4db9dc3 3dc372f844d6133 faff415befe c64d55a76bd21c9 664080f76a) a6e6af521f2b0aa a5923041a1)
Closes-bug: #2015377
(cherry picked from commit 267efd298479d66
(cherry picked from commit 0681f8b3ad43aaf