76578393ab401a33084921c4355af8e82c5d02ee
In case when during adding device to the namespace, device will be "shy" and will disappear for a moment and NetworkInterfaceNotFound exception will be raised, we need to reset device.namespace to be None. Otherwise, in the next attempt of adding interface to namespace, when it will be added back to ovs (and will be in global scope), Neutron will already look for it in the "namespace" and that will always be failing. Closes-bug: #1961740 Change-Id: Ie9331c72c44084b0a382598c3359214cce2f2ebd
OpenStack Neutron
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:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/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.
Languages
Python
99.6%
Shell
0.4%