Bug 2102231

Summary:	Correct DNS validation for destination namespace
Product:	Migration Toolkit for Containers	Reporter:	Javier Coscia <jcoscia>
Component:	Controller	Assignee:	Jason Montleon <jmontleo>
Status:	CLOSED ERRATA	QA Contact:	ssingla
Severity:	urgent	Docs Contact:	Richard Hoch <rhoch>
Priority:	urgent
Version:	1.7.1	CC:	ernelson, jmontleo, prajoshi, rjohnson
Target Milestone:	---
Target Release:	1.7.3
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-08-02 07:45:55 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 Javier Coscia 2022-06-29 13:55:59 UTC

Description of problem:

MigPlan cannot be validated because destination namespace starts with a non-alphabetic character

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

OCP 4.9.23
mtc-operator.v1.7.1
oadp-operator.v1.0.3

How reproducible:

Always

Steps to Reproduce:
1. Create a MigPlan with a source/destination (in case of migration of PVs between storage classes) namespace which starts with a numeric character like 3scale

Actual results:

MigPlan validation fails with: Destination Namespaces [0-9...] are not DNS compliant

Expected results:

We should not block migplan if destination namespace starts with a number. i.e.: 3scale

Additional info:

Validation introduced through https://bugzilla.redhat.com/show_bug.cgi?id=2005848

According to internal discussion we might need to change to RFC1123 rather than 1035, only difference is first char in 1123 is alphanumeric rather than alphabetic

Comment 10 errata-xmlrpc 2022-08-02 07:45:55 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.3 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:5840