Red Hat Bugzilla – Bug 1538722
Registry push fails during build in S3 registry
Last modified: 2018-03-28 10:22:52 EDT
Description of problem: Registry push are failing for s3 registry during any build of quickstart app. I see following error in registry logs time="2018-01-25T16:14:06.240840753Z" level=error msg="response completed with error" err.code=unknown err.detail="s3aws: NotImplemented: A header you provided implies functionality that is not implemented Version-Release number of selected component (if applicable): openshift v3.9.0-0.24.0 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.8 Steps to Reproduce: 1. create cluster with s3 registry backend 2. create quickstart app and watch build and registry logs Actual results: Registry push fails during build Expected results: Registry push should succeed. Additional info: Attached build and registry logs.
Created attachment 1386209 [details] build log
From https://github.com/aws/aws-sdk-go/issues/1379: > This is a known issue with the service using 1.6.2 of the SDK or earlier. From https://github.com/docker/distribution/blob/release/2.6/Godeps/Godeps.json: > "ImportPath": "github.com/aws/aws-sdk-go/aws", > "Comment": "v1.2.4", I'm still investigating, but it looks like we need to update our aws-sdk-go.
This works in the 3.9.0-0.23.0 docker-registry image but not in 3.9.0-0.24.0
https://github.com/openshift/image-registry/pull/56
Moving to MODIFIED until a puddle is available for QA
Verified on 3.9.0-0.31.0, s3 registry works as expected.
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:0489