Red Hat Bugzilla – Bug 1586212
[3.7] OpenShift container registry is not able to use eu-west-3 for s3 storage.
Last modified: 2018-06-27 03:59:55 EDT
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
Sorry ignore my previous comment : Customer wants this feature to be implemented to version 3.7
Verified openshift v3.7.53 kubernetes v1.7.6+a08f5eeb62
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
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