Bug 2032566

Summary:	Cluster-ingress-router does not support Azure Stack
Product:	OpenShift Container Platform	Reporter:	Patrick Dillon <padillon>
Component:	Networking	Assignee:	Patrick Dillon <padillon>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	aos-bugs, bmcelvee, mmasters
Version:	4.9
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: To configure DNS on Azure using IPI, the ingress operator requires an ARM endpoint. This endpoint is well known for public Azure and Government Azure, but it must be provided through configuration for Azure Stack Hub. Consequence: The ingress operator failed to configure a wildcard DNS record for ingress on Azure Stack Hub IPI, which prevented ingress from working. Fix: The ingress operator was changed to check the cluster infrastructure config object for the ARM endpoint provided by the installer. Result: The ingress operator now uses the configured ARM endpoint to configure DNS on Azure Stack Hub IPI so ingress works properly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:33:57 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:
Bug Depends On:
Bug Blocks:	2032677

Description Patrick Dillon 2021-12-14 17:55:51 UTC

Description of problem:The cluster-ingress-operator does not support Azure Stack Hub. This was not noticed for the UPI release in 4.9, because we were deleting the public records from the manifests as part of the installation. 


OpenShift release version: 4.9 (UPI) & 4.10 (IPI)


Cluster Platform: Azure Stack Hub


How reproducible: Always


Steps to Reproduce (in detail):
1. Perform IPI install or UPI install without deleting public zone



Actual results: Various failures while trying to initialize DNS client


Expected results: Create *.apps

Comment 2 Miciah Dashiel Butler Masters 2021-12-14 18:58:28 UTC

As this isn't a regression, I'm assuming this is not a blocker (but it is high priority).  Please correct me if I'm wrong.

Comment 5 Hongan Li 2021-12-23 03:49:39 UTC

verified with 4.10.0-0.nightly-2021-12-21-130047 and passed

Comment 7 Brandi Munilla 2022-02-10 20:37:47 UTC

Hi, if there is anything that customers should know about this bug or if there are any important workarounds that should be outlined in the bug fixes section OpenShift Container Platform 4.10 release notes, please update the Doc Type and Doc Text fields. If not, can you please mark it as "no doc update"? Thanks!

Comment 9 errata-xmlrpc 2022-03-10 16:33:57 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056