Bug 1957583

Summary: Routes are not getting created when using hostname without FQDN standard
Product: OpenShift Container Platform Reporter: Jobin A T <jat>
Component: NetworkingAssignee: aos-network-edge-staff <aos-network-edge-staff>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, mmasters
Version: 4.7   
Target Milestone: ---   
Target Release: ---   
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: 2021-05-07 16:04:30 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 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 ***