Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1414438 - the s3 storage registry driver does not include the AWS ca-central-1 region
the s3 storage registry driver does not include the AWS ca-central-1 region
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry (Show other bugs)
3.4.0
All All
urgent Severity urgent
: ---
: 3.3.1
Assigned To: Michal Fojtik
zhou ying
:
Depends On: 1412367 1414439
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-18 09:01 EST by Michal Fojtik
Modified: 2017-02-22 13:11 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1412367
Environment:
Last Closed: 2017-02-22 13:11:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0289 normal SHIPPED_LIVE OpenShift Container Platform 3.4.1.7, 3.3.1.14, and 3.2.1.26 bug fix update 2017-02-22 18:10:04 EST

  None (edit)
Comment 2 zhou ying 2017-02-03 01:56:50 EST
Confirmed with the latest OCP3.3.1 , the issue has fixed:
openshift version
openshift v3.3.1.12
kubernetes v1.3.0+52492b4
etcd 2.3.0+git


[root@ip-172-18-5-234 origin]# oc get po 
NAME                       READY     STATUS    RESTARTS   AGE
docker-registry-3-5quy4    1/1       Running   0          3m
registry-console-1-2ga3s   1/1       Running   0          17m
router-1-sl4t2             1/1       Running   0          17m


[root@ip-172-18-5-234 origin]# oc exec -it docker-registry-3-5quy4 more /etc/registry/config.yml
version: 0.1
log:
  level: debug
http:
  addr: :5000
storage:
  delete:
    enabled: true
  cache:
    blobdescriptor: inmemory
  s3:
    accesskey: xxxxxx
    secretkey: yyyyyy
    region: ca-central-1
    bucket: xyxhyxxxxxxxx
Comment 4 errata-xmlrpc 2017-02-22 13:11:00 EST
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-2017:0289

Note You need to log in before you can comment on or make changes to this bug.