Bug 1258562 - avahi-cname-manager validity check too restrictive
avahi-cname-manager validity check too restrictive
Product: OpenShift Origin
Classification: Red Hat
Component: Networking (Show other bugs)
All All
unspecified Severity low
: ---
: ---
Assigned To: Abhishek Gupta
Meng Bo
Depends On:
  Show dependency treegraph
Reported: 2015-08-31 12:06 EDT by Trent Nadeau
Modified: 2017-05-31 14:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-05-31 14:22:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Trent Nadeau 2015-08-31 12:06:41 EDT
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):

How reproducible:

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 14:22:11 EDT
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.