Bug 1809622 - openshift-ingress-operator fails in AWS China
Summary: openshift-ingress-operator fails in AWS China
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.4.0
Assignee: Dan Mace
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On: 1805224
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-03 14:39 UTC by Dan Mace
Modified: 2022-08-04 22:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1805224
Environment:
Last Closed: 2020-05-13 22:00:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 367 0 None closed [release-4.4] Bug 1809622: Add support for AWS China region route53 Service 2020-03-09 01:14:54 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 22:00:21 UTC

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
Note You need to log in before you can comment on or make changes to this bug.