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/ +/879913 /opendev. org/openstack/ neutron/ commit/ 267efd298479d66 c64d55a76bd21c9 664080f76a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 267efd298479d66 c64d55a76bd21c9 664080f76a
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.
Change-Id: I943f2fb4db9dc3 3dc372f844d6133 faff415befe
Closes-bug: #2015377