+++ 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
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"