0681f8b3ad
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 267efd2984)
12 lines
523 B
YAML
12 lines
523 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fix an issue in the OVN driver where network metadata could
|
|
become unavailable if the metadata port was ever deleted, even
|
|
if accidental. To re-create the port, a user can now disable,
|
|
then enable, DHCP for one of the subnets associated with the
|
|
network using the Neutron API. This will try and create the
|
|
port, similar to what happens in the DHCP agent for ML2/OVS.
|
|
For more information, see bug `2015377
|
|
<https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2015377>`_.
|