Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1538722

Summary: Registry push fails during build in S3 registry
Product: OpenShift Container Platform Reporter: Vikas Laad <vlaad>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: Dongbo Yan <dyan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, mifiedle
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: downgrade of the dependency aws-sdk-go Consequence: write to s3 fails Fix: upgrade the dependency Result: bug fixed
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-28 14:22:32 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
build log none

Description Vikas Laad 2018-01-25 16:42:02 UTC 
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.
Comment 2 Vikas Laad 2018-01-25 16:45:22 UTC 
Created attachment 1386209 [details]
build log
Comment 3 Oleg Bulatov 2018-01-25 16:53:54 UTC 
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.
Comment 4 Mike Fiedler 2018-01-25 17:31:53 UTC 
This works in the 3.9.0-0.23.0 docker-registry image but not in 3.9.0-0.24.0
Comment 7 Oleg Bulatov 2018-01-26 13:56:37 UTC 
https://github.com/openshift/image-registry/pull/56
Comment 8 Mike Fiedler 2018-01-26 17:40:44 UTC 
Moving to MODIFIED until a puddle is available for QA
Comment 10 Vikas Laad 2018-01-29 18:34:54 UTC 
Verified on 3.9.0-0.31.0, s3 registry works as expected.
Comment 13 errata-xmlrpc 2018-03-28 14:22:32 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:0489