Bug 2055658 - [MTC UI] Cancel button on “Migrations” page does not disappear when migration gets Failed/Succeeded with warnings
Summary: [MTC UI] Cancel button on “Migrations” page does not disappear when migration...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: UI
Version: 1.7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 1.7.2
Assignee: Mike Turley
QA Contact: Prasad Joshi
Richard Hoch
URL:
Whiteboard:
Depends On:
Blocks: 2057579
TreeView+ depends on / blocked
 
Reported: 2022-02-17 13:15 UTC by ssingla
Modified: 2022-07-01 09:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2057579 (view as bug list)
Environment:
Last Closed: 2022-07-01 09:52:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot (35.28 KB, image/png)
2022-02-17 13:15 UTC, ssingla
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-ui pull 1428 0 None open Bug 2055658: Always hide Cancel action if it would be disabled 2022-05-11 16:58:28 UTC
Github konveyor mig-ui pull 1429 0 None open [Backport - 1.7.2] Bug 2055658: Always hide Cancel action if it would be disabled 2022-05-11 16:58:28 UTC
Red Hat Product Errata RHSA-2022:5483 0 None None None 2022-07-01 09:53:10 UTC

Description ssingla 2022-02-17 13:15:44 UTC
Created attachment 1861688 [details]
Screenshot

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.

Comment 1 Erik Nelson 2022-02-21 13:48:27 UTC
Can you confirm this always happens or only with an underlying platform of GCP?

Comment 2 ssingla 2022-02-21 15:03:56 UTC
Not specific to GCP. Always happen on other platforms also.

Comment 3 Erik Nelson 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.

Comment 4 ssingla 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 10 Prasad Joshi 2022-06-16 09:39:57 UTC
Verified with MTC 1.7.2 

metadata_nvr: openshift-migration-operator-metadata-container-v1.7.2-11

Cancel button is not visible in UI. 

Moving this to verified status.

Comment 16 errata-xmlrpc 2022-07-01 09:52:59 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.7.2 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:5483


Note You need to log in before you can comment on or make changes to this bug.