Ihar Hrachyshka e6878c12c3 ovn: first tear down old metadata namespaces, then deploy new ... While the reverse order may work, it's considered invalid by OVN and not guaranteed to work properly since OVN may not necessarily know which of two ports is the one to configure. This configuration also triggered a bug in OVN where tearing down a port after deploying a new one resulted in removing flows that serve the port. There is a patch up for review for OVN [1] to better handle multiple assignment of the same port, but it doesn't make the setup any more valid. [1] http://patchwork.ozlabs.org/project/ovn/patch/20221114092437.2807815-1-xsimonar@redhat.com/ Conflicts: neutron/agent/ovn/metadata/agent.py Closes-Bug: #1997092 Change-Id: Ic7dbc4e8b00423e58f69646a9e3cedc6f72d6c63 (cherry picked from commit 3093aaab13)		2022-11-18 22:12:31 +00:00
..
metadata	ovn: first tear down old metadata namespaces, then deploy new	2022-11-18 22:12:31 +00:00
__init__.py	[OVN] Move OVN metadata agent	2019-12-09 10:48:39 +00:00
metadata_agent.py	[OVN] Change DevStack to use the local OVN driver	2020-01-16 09:28:43 +00:00