Bug 2004553 - MTC shouldn't allow triggering State migration when IDVM=true
Summary: MTC shouldn't allow triggering State migration when IDVM=true
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: UI
Version: 1.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 1.7.0
Assignee: Pranav Gaikwad
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-15 14:34 UTC by Xin jiang
Modified: 2022-03-24 06:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-24 06:32:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 1257 0 None open Bug 2004553: Validation for indirect migration types and state transfer 2022-01-24 20:38:24 UTC
Red Hat Product Errata RHBA-2022:1043 0 None None None 2022-03-24 06:32:38 UTC

Description Xin jiang 2021-09-15 14:34:07 UTC 
Description of problem:
it still allows to trigger State migration when IDVM mode enabled. 

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

How reproducible:
always

Steps to Reproduce:
1. deploy an application with PVCs on source cluster

2. Create a migplan with IDIM and IDVM

3. trigger State migration from MTC console



Actual results:
the State migration is triggered and failed


Expected results:
the State migration shouldn't be allowed to trigger. 

Pranav:
We have only trusted direct migrations with state. We do not intend to support indirect migrations. 

Additional info:
Comment 6 errata-xmlrpc 2022-03-24 06:32:26 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 (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
Note You need to log in before you can comment on or make changes to this bug.