+++ This bug was initially created as a clone of Bug #2055658 +++ Description of the problem: When we execute a migration from the migration plan and it fails due to some reason, or it gets succeeded but with some warning, the cancel button does not disappear from the Migrations page and it is just disabled. Severity: Low Version-Release number of selected component (if applicable): SOURCE CLUSTER: GCP 4.6 MTC 1.7.0 TARGET CLUSTER: GCP 4.9 MTC 1.7.0 Steps to Reproduce: 1. Create a project in source cluster $ oc new-project test 2. Deploy an application in source cluster $ oc new-app cakephp-mysql-persistent 3. Break connection with registry oc patch configs.imageregistry.operator.openshift.io cluster -p '{"spec":{"managementState": "Unmanaged"} }' --type='merge'; Oc -n openshift-image-registry patch service image-registry -p '{"spec":{"selector": {"docker-registry": "defaultX"}} }' --type='merge'; 3. Create a migplan from UI using the project 4. Run Cutover migration. 5. After it fails, go to the Migrations page for that migplan. Actual Result: Cancel button is not yet disappeared from there and just got disabled. Expected Result: Cancel button should disappear from there as it happens in other successful or cancelled migrations. --- Additional comment from Erik Nelson on 2022-02-21 13:48:27 UTC --- Can you confirm this always happens or only with an underlying platform of GCP? --- Additional comment from on 2022-02-21 15:03:56 UTC --- Not specific to GCP. Always happen on other platforms also. --- Additional comment from Erik Nelson on 2022-02-21 20:06:21 UTC --- What happens if you re-cancel the migration? I need to determine if this is a blocking issue. --- Additional comment from on 2022-02-22 04:25:41 UTC --- The button gets disabled as shown in the screenshot attached, So i cannot re-cancel it after its failed/succeeded with warnings. Just the issue is that it should not even be visible. However, if i trigger the migration and cancel it normally, the cancel button gets disappeared.
Why was this BZ duplicated? Was the intention to have this one target a 1.6.x release?
Per Slack discussion, changing target release to 1.6.5
Verified with MTC 1.6.5 (prestage) metadata_nvr: openshift-migration-operator-metadata-container-v1.6.5-9 Cancel button is not visible for failed and cancelled migrations. 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 (Moderate: Migration Toolkit for Containers (MTC) 1.6.5 security and bug fix update), 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/RHSA-2022:4814