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)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/881315 /opendev. org/openstack/ neutron/ commit/ 78a24a3a75f4a36 5ec4c49e5645d5c a17c2e49b5
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit 78a24a3a75f4a36 5ec4c49e5645d5c a17c2e49b5
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)
Closes-bug: #2015377
(cherry picked from commit 267efd298479d66