Bug 1258562 - avahi-cname-manager validity check too restrictive
Summary: avahi-cname-manager validity check too restrictive
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: Networking
Version: 2.x
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-31 16:06 UTC by Trent Nadeau
Modified: 2017-05-31 18:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-31 18:22:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.