Bug 1805224

Summary:	openshift-ingress-operator fails in AWS China
Product:	OpenShift Container Platform	Reporter:	Wang Haoran <haowang>
Component:	Networking	Assignee:	Miciah Dashiel Butler Masters <mmasters>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, dmace
Version:	4.4
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The ingress operator did not use the appropriate Route 53 API endpoint when running in AWS China regions. Consequence: The ingress operator failed to configure DNS when it was running in AWS China regions. Fix: The ingress operator now detects when it is running in AWS China regions and configures the appropriate API endpoint. Result: The ingress operator can now configure DNS in Route 53 in AWS China regions.	Story Points:	---
Clone Of:
Clones:	1809622 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:16:23 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:	1809622

Description Wang Haoran 2020-02-20 14:10:40 UTC

Description of problem:
The operator didn't work because of the api endpoints and region are not correct.
In aws china, the route53 api endpoint is https://api.route53.cn or https://route53.amazonaws.com.cn

PR : https://github.com/openshift/cluster-ingress-operator/pull/361
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Wang Haoran 2020-03-12 07:23:12 UTC

Verified with : registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-03-12-031748

Comment 5 errata-xmlrpc 2020-07-13 17:16:23 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, 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-2020:2409