Bug 1957583 - Routes are not getting created when using hostname without FQDN standard
Summary: Routes are not getting created when using hostname without FQDN standard
Keywords:
Status: CLOSED DUPLICATE of bug 1957584
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: aos-network-edge-staff
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-06 04:51 UTC by Jobin A T
Modified: 2022-08-04 22:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-07 16:04:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jobin A T 2021-05-06 04:51:32 UTC
Description of problem:
Routes are not getting created when using hostname without FQDN standard 
In OCP 3.11 we are able to create routes using hostname "pipequery" with out the FQDN standard.
But in OCP4.7 we are not able to create the same routes. while creating we are getting the below error.

The Route "httpd" is invalid: spec.host: Invalid value: "pipequery": host must conform to DNS 1123 naming conventions: [spec.host: Invalid value: "pipequery": should be a domain with at least two segments separated by dots] 

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

How reproducible:
Using the below Reproduce steps we can reproduce this issue.
Using the same step in both OCP 3.11 and 4.11 we will give us the difference.
In 3.11 route will create with out any issue.
But in 4.7 route will not create.

Steps to Reproduce:

1. oc new-project demo
2. oc new-app httpd
3. oc expose svc/httpd --hostname=pipequery

Actual results:
The Route "httpd" is invalid: spec.host: Invalid value: "pipequery": host must conform to DNS 1123 naming conventions: [spec.host: Invalid value: "pipequery": should be a domain with at least two segments separated by dots]

Expected results:
Route should create with out any warning.

Additional info:

Comment 1 Miciah Dashiel Butler Masters 2021-05-07 16:04:30 UTC

*** This bug has been marked as a duplicate of bug 1957584 ***


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