Bug 1810865

Summary:	Cloud Credential operator failed to run on AWS China regions
Product:	OpenShift Container Platform	Reporter:	Wang Haoran <haowang>
Component:	Cloud Credential Operator	Assignee:	Devan Goodwin <dgoodwin>
Status:	CLOSED ERRATA	QA Contact:	wang lin <lwan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	jdiaz, lwan
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1811093 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:45:02 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:	1811093
Bug Blocks:

Description Wang Haoran 2020-03-06 04:24:58 UTC

Description of problem:

Problem:
The cloud credential operator not works in aws china, because they are not using the correct api endpoint and regions.

Errors:

error while validating cloud credentials: failed checking create cloud creds: error gathering AWS credentials details: error querying username: InvalidClientTokenId: The security token included in the request is invalid.\n\tstatus code: 403, request id: 23761878-8741-4472-a1a4-5e959e055725
Ref:
Aws china api endpoints:
https://docs.amazonaws.cn/en_us/aws/latest/userguide/endpoints-arns.html

Version-Release number of selected component (if applicable):


How reproducible:

always
Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Wang Haoran 2020-03-11 02:28:23 UTC

This works as expected on :  registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-03-10-002851

Comment 4 Devan Goodwin 2020-04-29 12:11:59 UTC

I do not believe this bug ever saw customers as the AWS China support was net new. Setting no docs required.

Comment 6 errata-xmlrpc 2020-05-04 11:45:02 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