Bug 1845092

Summary:	Automatic rollback of migrated workloads is not configurable
Product:	Migration Toolkit for Containers	Reporter:	John Matthews <jmatthew>
Component:	General	Assignee:	Derek Whatley <dwhatley>
Status:	CLOSED NOTABUG	QA Contact:	Xin jiang <xjiang>
Severity:	high	Docs Contact:	Avital Pinnick <apinnick>
Priority:	unspecified
Version:	1.3.0	CC:	dwhatley, ernelson, rjohnson, sregidor, xjiang
Target Milestone:	---
Target Release:	1.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1844638	Environment:
Last Closed:	2021-01-21 16:04:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1844638

Description John Matthews 2020-06-08 13:00:17 UTC

+++ This bug was initially created as a clone of Bug #1844638 +++

Description of problem:
When a migration fails, the user running a migration has no option to leave partially migrated workloads in place on the destination so that they can finish the migration manually.

Version-Release number of selected component (if applicable):
1.2.0

How reproducible:
Always

Steps to Reproduce:
1. Run a migration
2. Encounter an error

Actual results:
Migration enters failed state and then runs "FailedItinerary" which deletes resources from target cluster and scales them back up on source


Expected results:
User is given a configuration option to allow for enabling or disabling of automatic rollback functionality


Additional info:

--- Additional comment from Derek Whatley on 2020-06-05 20:58:51 UTC ---

PRs adding a config switch for this are up, working on getting them tested.

mig-controller: https://github.com/konveyor/mig-controller/pull/560
mig-operator: https://github.com/konveyor/mig-operator/pull/370

Comment 4 Sergio 2021-01-21 16:04:20 UTC

In MTC 1.4 the rollback can be triggered manually at will. Hence, the automatic rollback option in case of failure has been removed. If the user wants to rollback a failed migration he only has to execute a Rollback (it was not possible before 1.4.0).

We close the BZ as "NOT A BUG"