Rodolfo Alonso Hernandez 7173bd4e98 [DHCP] Do not force the DHCP disable call in a network creation
During a network creation, the code added to support multiple network
segments [1] was first disabling any existing DHCP namespace (including
the namespace deletion, the driver removal and the DHCP port deletion)
and the re-creating it again. The execution of both actions one after
the other was triggering a race condition where the DHCP namespace was
left without the DHCP port.

[1]https://review.opendev.org/c/openstack/neutron/+/840421

Closes-Bug: #2073464
Change-Id: Ic688d1c721511868b7bd9943bb679c4cb91b1a60
2024-07-18 08:19:55 +00:00
2016-06-28 22:46:19 +02:00
2024-06-06 11:13:54 +05:30
2024-05-02 10:46:27 +00:00
2019-04-19 19:38:27 +00:00
2014-05-16 13:40:04 -04:00
2024-05-15 16:13:38 +02:00
2023-08-21 13:57:00 +00:00
2024-02-08 10:34:10 -05:00
2023-03-28 06:59:20 +00:00
2024-01-12 17:44:09 +09:00
2024-05-21 13:17:36 -04:00

OpenStack Neutron

image

Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).

To learn more about neutron:

If you would like to contribute to Neutron, please read the file CONTRIBUTING.rst or see the Neutron contributor guide:

https://docs.openstack.org/neutron/latest/contributor/contributing.html

Get in touch via email. Use [Neutron] in your subject.

Description
OpenStack Networking (Neutron)
Readme 1,016 MiB
Languages
Python 99.7%
Shell 0.3%