Bug 1586212

Summary:	[3.7] OpenShift container registry is not able to use eu-west-3 for s3 storage.
Product:	OpenShift Container Platform	Reporter:	Ryan Howe <rhowe>
Component:	Image Registry	Assignee:	Alexey Gladkov <agladkov>
Status:	CLOSED ERRATA	QA Contact:	Dongbo Yan <dyan>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.6.0	CC:	aos-bugs, bparees, jkaur, rhowe, rkant, tatanaka
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1587996 1587997 (view as bug list)		Environment:
Last Closed:	2018-06-27 07:59:11 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:	1587996, 1587997

Description Ryan Howe 2018-06-05 18:02:11 UTC

Description of problem:
 
  OpenShift container registry is not able to use eu-west-3 for s3 storage. 

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

- kubernetes_version=v1.6.1+5115d708d7 + 
- openshift_version=v3.6.173.0.117   +

How reproducible:
100% 

Additional info:

Similar commit in the past for other regions: 

 https://github.com/openshift/origin/commit/e638fa47cc16d7822a2e7c0eaf673c9460b6f961#diff-765e29431711f7f036a65e2439a3b399


Current: 
  https://github.com/openshift/origin/blob/master/vendor/github.com/docker/distribution/registry/storage/driver/s3-aws/s3.go#L104-L122

  https://github.com/docker/distribution/blob/master/registry/storage/driver/s3-aws/s3.go#L107-L122

Comment 3 Jaspreet Kaur 2018-06-06 10:25:28 UTC

Sorry ignore my previous comment : 

Customer wants this feature to be implemented to version 3.7

Comment 9 Dongbo Yan 2018-06-15 04:21:48 UTC

Verified
openshift v3.7.53
kubernetes v1.7.6+a08f5eeb62

Comment 10 Dongbo Yan 2018-06-15 08:32:50 UTC

Reproduce steps:
1.create a s3 bucket located in eu-west-3 region
2.launch an openshift cluster which internal registry use above s3 bucket as the registry storage
3.pull/push image to internal registry

actual results:
could pull and push to internal registry successfully

Comment 14 errata-xmlrpc 2018-06-27 07:59:11 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-2018:2009