Bug 1867972

Summary: [aws-custom-region]cluster can not be destroyed due to error "InvalidSignatureException: Credential should be scoped to a valid region, not 'us-east-1'" in us-gov region
Product: OpenShift Container Platform Reporter: Yunfei Jiang <yunjiang>
Component: InstallerAssignee: Abhinav Dahiya <adahiya>
Installer sub component: openshift-installer QA Contact: Yunfei Jiang <yunjiang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: adahiya
Version: 4.6   
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:27:30 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:
Attachments:
Description Flags
install log none

Description Yunfei Jiang 2020-08-11 09:54:19 UTC
Created attachment 1711055 [details]
install log

Description of problem: 
Install a private cluster in us-gov-west-1 region, failed, when destroying it, got an infinite error:
INFO get tagged resources: InvalidSignatureException: Credential should be scoped to a valid region, not 'us-east-1'.
    status code: 400, request id: 7ee2b7d1-1de2-4356-8e26-8478abf2d36c
INFO get tagged resources: InvalidSignatureException: Credential should be scoped to a valid region, not 'us-east-1'.
    status code: 400, request id: 6ec75a70-bdfd-4dfe-823d-87bd8a381cad


Version-Release number of the following components: 
4.6.0-0.nightly-2020-08-09-151434
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. Create a private cluster in AWS us gov regions, failed
2. Destroy the failed cluster
 
Actual results: 
infinite error:
INFO get tagged resources: InvalidSignatureException: Credential should be scoped to a valid region, not 'us-east-1'.
    status code: 400, request id: 7ee2b7d1-1de2-4356-8e26-8478abf2d36c
 
Expected results: 
destroy cluster successfully

Additional info:

Comment 1 Abhinav Dahiya 2020-08-11 17:05:55 UTC
Can you include the metadata.json file ?

Comment 2 Yunfei Jiang 2020-08-12 02:36:19 UTC
metadata.json

{"clusterName":"yunjiang-4ep","clusterID":"205f25d5-4f96-4429-85cf-f846ffc17e80","infraID":"yunjiang-4ep-rhpgh","aws":{"region":"us-gov-west-1","serviceEndpoints":[{"name":"ec2","url":"https://ec2.us-gov-west-1.amazonaws.com"},{"name":"elasticloadbalancing","url":"https://elasticloadbalancing.us-gov-west-1.amazonaws.com"},{"name":"s3","url":"https://s3.us-gov-west-1.amazonaws.com"},{"name":"tagging","url":"https://tagging.us-gov-west-1.amazonaws.com"}],"identifier":[{"kubernetes.io/cluster/yunjiang-4ep-rhpgh":"owned"},{"openshiftClusterID":"205f25d5-4f96-4429-85cf-f846ffc17e80"}]}}

Comment 5 Yunfei Jiang 2020-08-13 10:22:02 UTC
Verified. PASS.
version: 4.6.0-0.nightly-2020-08-13-055915

Comment 7 errata-xmlrpc 2020-10-27 16:27:30 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 (OpenShift Container Platform 4.6 GA Images), 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:4196

Comment 8 Red Hat Bugzilla 2023-09-14 06:05:38 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days