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: I943f2fb4db9dc33dc372f844d6133faff415befe
Closes-bug: #2015377
(cherry picked from commit 267efd298479d66c64d55a76bd21c9664080f76a)
(cherry picked from commit 0681f8b3ad43aafa6e6af521f2b0aaa5923041a1)
(cherry picked from commit 47b9511ec5da9b8c8721316f7671bc794c848147)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/883535 /opendev. org/openstack/ neutron/ commit/ d636685f497f5ca 2784f92f5d5b8bd 24cf35c170
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit d636685f497f5ca 2784f92f5d5b8bd 24cf35c170
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 c64d55a76bd21c9 664080f76a) a6e6af521f2b0aa a5923041a1) c8721316f7671bc 794c848147)
Closes-bug: #2015377
(cherry picked from commit 267efd298479d66
(cherry picked from commit 0681f8b3ad43aaf
(cherry picked from commit 47b9511ec5da9b8