Bug 2040693

Summary:	“Replication repository” wizard has no validation for name length
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	UI	Assignee:	Ian <ibolton>
Status:	CLOSED ERRATA	QA Contact:	mohamed <midays>
Severity:	low	Docs Contact:	Richard Hoch <rhoch>
Priority:	low
Version:	1.6.3	CC:	ernelson, ibolton, midays, 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:	2040166	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:	2040166
Bug Blocks:

Description Erik Nelson 2022-01-14 14:27:44 UTC

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

Description of problem: Replication repository name length has no validation and hence if you enter a really long name, the UI behaves unexpectedly.
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 Replication Repository” and enter a really long name around 400 chars and fill the other details.
3. Click on “Add Repository”
 

Actual Result: 

Either the repository is added to the UI and the Replication repositories UI card goes out of the screen.

Or, The UI keeps validating the connection forever.


Expected Result: There should be a proper validation on Replication repository name length.

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