Bug 2004553

Summary:	MTC shouldn't allow triggering State migration when IDVM=true
Product:	Migration Toolkit for Containers	Reporter:	Xin jiang <xjiang>
Component:	UI	Assignee:	Pranav Gaikwad <pgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	1.6.0	CC:	ernelson, rjohnson, sgoodman, ssingla
Target Milestone:	---
Target Release:	1.7.0
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-03-24 06:32:26 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:

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