Description of the problem: If we cancel a rollback, the migplan moves to the Canceled Rollback state but “Rollback” option gets disabled for the migration plan. Severity: Medium Version-Release number of selected component (if applicable): SOURCE CLUSTER: AWS 4.6 MTC 1.7.0 TARGET CLUSTER: AWS 4.9 MTC 1.7.0 How reproducible: Always Steps to Reproduce: 1. Deploy any application in the source cluster 2. Login to the MTC console and Create a migplan and select migration type as Full migration. 3. Execute cutover 4. Execute Rollback and cancel it before it finishes. 5. Open the Kebab menu besides the migplan status Actual Result: “Rollback” is disabled and “Stage” & “Cutover” are enabled. Expected Result: “Rollback” option should be enabled and “Stage” & “Cutover” should be disabled as rollback was cancelled.
Verified with MTC 1.7.0 (pre-stage) metadata_nvr: openshift-migration-operator-metadata-container-v1.7.0-33 image: registry.redhat.io/rhmtc/openshift-migration-controller-rhel8@sha256:c08211e7fa12e8a12ea07ed0f31bf24bdd4cc95b166a34d826e3240a0534e622 After cancelling the rollback, the rollback option is getting enabled. stage and cutover options are disabled. Moving this to Verified status.
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