Bug 2014938

Summary: Ingress operator not creating wildcard route for hypershift clusters
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Cesar Wong <cewong>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, jiezhao, mmasters
Version: 4.9   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-22 21:47:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2011972    
Bug Blocks:    

Description OpenShift BugZilla Robot 2021-10-18 03:27:31 UTC
+++ This bug was initially created as a clone of Bug #2011972 +++

Description of problem:
When running in a hypershift cluster on AWS, with controlPlaneTopology set to "External", the ingress operator does not create a DNS entry for the default ingress controller.

OpenShift release version:
4.9

How reproducible: Always


Steps to Reproduce (in detail):
1. Create a hypershift cluster with control plane topology set to "External"
2. Wait for the ingress operator to report "Available"


Actual results:
The ingress operator never reports Available because it did not create a wildcard entry for its default ingress controller.


Expected results:
The ingress operator reports available

Comment 6 errata-xmlrpc 2021-11-22 21:47:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.9.8 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4712