Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1809622

Summary:	openshift-ingress-operator fails in AWS China
Product:	OpenShift Container Platform	Reporter:	Dan Mace <dmace>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, dmace, haowang, hongli, mmasters
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1805224	Environment:
Last Closed:	2020-05-13 22:00:20 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:	1805224
Bug Blocks:

Description Dan Mace 2020-03-03 14:39:22 UTC

+++ This bug was initially created as a clone of Bug #1805224 +++

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 Hongan Li 2020-03-09 06:10:49 UTC

Tested with 4.4.0-0.nightly-2020-03-06-234832 on several AWS regions and no regression.

Waiting for the feedback from Haoran Wang if pass on AWS China region.

Comment 4 Hongan Li 2020-03-11 02:22:34 UTC

Haoran has confirmed that it works on AWS China region now. so moving to verified.

Comment 6 errata-xmlrpc 2020-05-13 22:00:20 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:0581