Bug 1258562

Summary:	avahi-cname-manager validity check too restrictive
Product:	OKD	Reporter:	Trent Nadeau <tanadeau>
Component:	Networking	Assignee:	Abhishek Gupta <abhgupta>
Status:	CLOSED WONTFIX	QA Contact:	Meng Bo <bmeng>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	aos-bugs, eparis
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-31 18:22:11 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 Trent Nadeau 2015-08-31 16:06:41 UTC

Description of problem:
When using mDNS for development, if the namespace or app name contains a number, adding the CNAME alias will fail. This is a valid domain name and is allowed by OpenShift, which constrains both to alphanumeric characters.

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

How reproducible:
Always

Steps to Reproduce:
1. Set up use of mDNS
2. Create app and/or namespace with a digit.
3. Deploy as normal

Actual results:
400 Invlaid CNAME
Note that the typo is in the original message.

Expected results:
No errors

Additional info:
Regex check is at https://github.com/openshift/origin-server/blob/master/extras/avahi-cname-manager/bin/avahi-cname-manager#L85 among other places.

Comment 1 Eric Paris 2017-05-31 18:22:11 UTC

We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.