Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1948579

Summary:	[ovn] Migration tool is not resilient enough to errors
Product:	Red Hat OpenStack	Reporter:	Daniel Alvarez Sanchez <dalvarez>
Component:	python-networking-ovn	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Eran Kuris <ekuris>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	apevec, jamsmith, jlibosva, jmelvin, lhh, lmartins, majopela, scohen
Target Milestone:	---	Keywords:	FutureFeature
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:51:29 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 Daniel Alvarez Sanchez 2021-04-12 14:04:20 UTC

Today, if the migration process fails at some point, there's a need for manual intervention due to the lack of resilience of the tool/process.

For example, if some issue happens in the activate-ovn phase [0] or in the middle of the process, such as [1] when changing the network type to Geneve the cloud is left in an intermediate state that it is neither on ML2/OVS nor ML2/OVN and requires engineering intervention to complete the process.

A daemon/agent running on all the nodes could help that tracks the current state of the migration, retry on errors and maybe even allow reverting things back if all goes wrong.

[0] https://github.com/openstack/neutron/blob/master/tools/ovn_migration/tripleo_environment/playbooks/roles/migration/templates/activate-ovn.sh.j2

[1] https://github.com/openstack/neutron/blob/master/tools/ovn_migration/tripleo_environment/playbooks/ovn-migration.yml#L39

Comment 3 Jakub Libosvar 2022-01-06 14:51:29 UTC

In case migration fails, we should be able to revert to OVS using the revert mechanism tracked in bug 1823324

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

Comment 4 Red Hat Bugzilla 2023-09-18 00:25:46 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days