Bug 2058529

Summary: [MTC UI] Migrations Plan is missing the type for the state migration performed before upgrade
Product: Migration Toolkit for Containers Reporter: ssingla
Component: UIAssignee: Jaydip Gabani <jgabani>
Status: CLOSED ERRATA QA Contact: mohamed <midays>
Severity: low Docs Contact: Anjana Suparna Sriram <asriram>
Priority: low    
Version: 1.7.0CC: ernelson, midays, rjohnson
Target Milestone: ---Keywords: Reopened
Target Release: 1.7.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-01 09:52:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description ssingla 2022-02-25 09:12:10 UTC
Created attachment 1863284 [details]
Screenshot

Description of the problem:  When we create a migplan in 1.6 and execute the state migration with mapping PVC name from the MTC UI (e.x: test-data: test-data-new), the migplan identifies the migplan as state migration type but on going to the migrations page for the migplan, the type is missing.

Severity: Medium

Version-Release number of selected component (if applicable):
MTC 1.7.0

Steps to reproduce:

1.  Setup 1.6.3 MTC on both source and target clusters.
2. Deploy any application with PVC in the source cluster
3. Login to the MTC UI and Create a migration plan with the same namespace created in the last step.
4. Execute the state migration by mapping PVC name to a diff target PVC name
    Eg: test-data: test-data-new
5. After the migration is successful, Perform the MTC upgrade to 1.7.0
6. Reload the MTC UI
7. Go to the Migrations page for the migplan

Actual Results: The type of the migration performed before upgrade is missing
Expected Results: The type of the migration should be identified as Stage/Cutover

Comment 1 Erik Nelson 2022-03-01 18:01:43 UTC
Pushing to 1.7.1 as not a blocker

Comment 3 Erik Nelson 2022-05-11 17:09:11 UTC
I suspect the information for us to be able to render this correctly is not possible and this will turn into a WONTFIX, but let's take a look.

Comment 5 Erik Nelson 2022-06-15 19:47:07 UTC
1.6/1.5 will be deprecated in the near term; closing as WONTFIX.

Comment 6 Erik Nelson 2022-06-16 15:54:30 UTC
Pushing back to MODIFIED as jaydip had already added a fix for this.

Comment 11 mohamed 2022-06-19 15:30:57 UTC
Verified using MTC 1.7.2 prestage / openshift-migration-operator-metadata-container-v1.7.2-15

Comment 17 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