Bug 2057579

Summary:	[MTC UI] Cancel button on “Migrations” page does not disappear when migration gets Failed/Succeeded with warnings
Product:	Migration Toolkit for Containers	Reporter:	ssingla
Component:	UI	Assignee:	Mike Turley <mturley>
Status:	CLOSED ERRATA	QA Contact:	Prasad Joshi <prajoshi>
Severity:	low	Docs Contact:	Richard Hoch <rhoch>
Priority:	low
Version:	1.6.3	CC:	ernelson, ibolton, mturley, prajoshi, rjohnson, xjiang
Target Milestone:	---
Target Release:	1.6.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2055658	Environment:
Last Closed:	2022-05-31 09:49:05 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:	2055658
Bug Blocks:

Description ssingla 2022-02-23 16:12:22 UTC

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

Comment 2 Mike Turley 2022-05-11 16:26:37 UTC

Why was this BZ duplicated? Was the intention to have this one target a 1.6.x release?

Comment 3 Mike Turley 2022-05-12 16:31:03 UTC

Per Slack discussion, changing target release to 1.6.5

Comment 7 Prasad Joshi 2022-05-18 08:37:31 UTC

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.

Comment 12 errata-xmlrpc 2022-05-31 09:49:05 UTC

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