Ubuntu
neutron package

  1. Bug #2015377
  2. Comment #16

Comment 16 for bug 2015377

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/victoria)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/883555
Committed: https://opendev.org/openstack/neutron/commit/85befc96787a71634576fdc54404e264861997da
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit 85befc96787a71634576fdc54404e264861997da
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:
      neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py
      neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_db_sync.py

    Change-Id: I943f2fb4db9dc33dc372f844d6133faff415befe
    Closes-bug: #2015377
    (cherry picked from commit 267efd298479d66c64d55a76bd21c9664080f76a)
    (cherry picked from commit 0681f8b3ad43aafa6e6af521f2b0aaa5923041a1)
    (cherry picked from commit 47b9511ec5da9b8c8721316f7671bc794c848147)