Bug 2032566 - Cluster-ingress-router does not support Azure Stack
Summary: Cluster-ingress-router does not support Azure Stack
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Patrick Dillon
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks: 2032677
TreeView+ depends on / blocked
 
Reported: 2021-12-14 17:55 UTC by Patrick Dillon
Modified: 2022-08-04 22:35 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2022-03-10 16:33:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 686 0 None open Bug 2032566: Azure: Add Support for Azure Stack Hub 2021-12-14 17:58:25 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:34:19 UTC

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


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