Bug 2025910

Summary: Revert ML2/OVS to ML2/OVN migration
Product: Red Hat OpenStack Reporter: Slawek Kaplonski <skaplons>
Component: python-networking-ovnAssignee: OSP Team <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: apevec, astupnik, jlibosva, lhh, majopela, scohen
Target Milestone: betaKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-06 14:22:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Slawek Kaplonski 2021-11-23 11:28:55 UTC 
There need to be some tool which will be able to revert migration from ML2/OVS to ML2/OVN if e.g. something would go wrong during the migration.

As first step, lets focus only on the simple case which is revert of the migration if there were e.g. no new instances spawned on the ML2/OVN yet, so all is plugged still to the br-int as it was before migration.
In such case migration should:
1. Revert network type and mtu changes done in the neutron db,
2. prepare tripleo images with ML2/OVS,
3. remove ovn "agents" from the nodes,
4. We will see what more could be maybe needed...


This procedure will be very basic as first step. Later we can move on with some more complex use cases if that will be needed.
Comment 1 Jakub Libosvar 2022-01-06 14:22:05 UTC 

*** This bug has been marked as a duplicate of bug 1823324 ***