Bug 2040695

Summary:	[MTC UI] “Add Cluster” wizard stucks when the cluster name length is more than 63 characters
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	UI	Assignee:	Ian <ibolton>
Status:	CLOSED ERRATA	QA Contact:	ssingla
Severity:	low	Docs Contact:	Anjana Suparna Sriram <asriram>
Priority:	low
Version:	1.6.3	CC:	ernelson, ibolton, rjohnson, ssingla, xjiang
Target Milestone:	---
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:	2040169	Environment:
Last Closed:	2022-07-01 09:52:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2040169
Bug Blocks:

Description Erik Nelson 2022-01-14 14:30:11 UTC

+++ This bug was initially created as a clone of Bug #2040169 +++

Description of problem: 
While adding a new cluster to the MTC web console, The “Add Cluster” wizard keep validating the connection forever when the cluster name is more than 63 characters long.

Severity: Low

Version-Release number of selected component (if applicable):
MTC 1.6.3
SOURCE CLUSTER: AWS 4.6 MTC 1.6.3
TARGET CLUSTER: AWS 4.9 MTC 1.6.3

How reproducible:
Always


Steps to Reproduce:
1. Login to the MTC web console
2. Click on “Add Cluster” and enter a cluster name of more than 63 characters and fill the other details appropriately
3. Click on “Add Cluster”
 

Actual Result: 

The wizard keeps validating the connection forever.


Expected Result: There should be a proper error message for the name validation on entering a name longer than 63 characters.

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