Bug 2060244

Summary:	[MTC] DIM registry route need to be exposed to create inter-cluster state migration plans
Product:	Migration Toolkit for Containers	Reporter:	ssingla
Component:	General	Assignee:	Pranav Gaikwad <pgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Prasad Joshi <prajoshi>
Severity:	urgent	Docs Contact:	Richard Hoch <rhoch>
Priority:	urgent
Version:	1.7.0	CC:	ernelson, jmontleo, prajoshi, rjohnson
Target Milestone:	---
Target Release:	1.7.1
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-05-05 13:50:01 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 ssingla 2022-03-03 04:30:04 UTC

Description of the problem: To create an inter cluster state migration plan, DIM registry route needs to be exposed even when there is no DirectImage step during the state migration. If not provided, an error message is displayed while creating the migration plan.

Severity: Low

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

Steps to reproduce:

1.  Deploy any application with PVC in the source cluster
2.  Login to the MTC UI and create a new inter cluster state migration plan, and reach the PVC page. 


Actual Results: It shows an error message that:
“DIM is selected but registry route is not configured”

Expected Results:  The error message should not be there and it should allow creating the migplan and DirectImage step is not involved in the migration.

Comment 8 errata-xmlrpc 2022-05-05 13:50:01 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.1 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:1734