Fedora Account System
Red Hat Associate
Red Hat Customer
Description of the problem: When we create a new migration plan, the Rollback option is already active for the plan even before performing any stage/cutover/state migration Severity: Low Version-Release number of selected component (if applicable): SOURCE CLUSTER: GCP 4.6 MTC 1.6.3 TARGET CLUSTER: GCP 4.9 MTC 1.6.3 Steps to Reproduce: 1. Create a project in source cluster $ oc new-project test 2. Deploy an application in source cluster (Optional) $ oc new-app cakephp-mysql-persistent 3. Create a migplan from UI using the project 4. Click on migplan’s Kebab menu after Migplan is ready. Actual Result: Rollback option is enabled even before any stage/cutover/state migration is performed. Expected Result: Rollback option should not be enabled there as no migration has been performed yet.
Is this unique to GCP migrations, or does this always happen regardless of the underlying platforms?
Not specific to GCP, Always happens under any platforms.
https://github.com/konveyor/mig-ui/pull/1368 - PR brings changes that resolves this bug
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Migration Toolkit for Containers (MTC) 1.7.0 release advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:1043