Bug 1330558 - Error in registry logs: error authorizing context: authorization header with basic token required
Summary: Error in registry logs: error authorizing context: authorization header with...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Paul Weil
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 13:02 UTC by Mike Fiedler
Modified: 2016-04-26 13:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-26 13:15:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Mike Fiedler 2016-04-26 13:02:55 UTC
Description of problem:

level=error message in the registry logs for every push when configured for AWS S3 storage

time="2016-04-26T08:56:20.046087778-04:00" level=error msg="error authorizing context: authorization header with basic token required" go.version=go1.4.2 http.request.host="172.24.4.23:5000" http.request.id=749007be-4897-4289-af24-ece409f7420c http.request.method=GET http.request.remoteaddr="172.20.1.1:38358" http.request.uri="/v2/" http.request.useragent="docker/1.9.1 go/go1.4.2 kernel/3.10.0-367.el7.x86_64 os/linux arch/amd64" instance.id=a561f38d-2ea1-4fd6-b8d4-1185f6563c6d 

The message does not seem to affect the push, but is concerning to an end-user.

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


How reproducible: Always


Steps to Reproduce:
1.  Configure the registry to use AWS S3 storage
version: 0.1
log:
  level: debug
http:
  addr: :5000
auth:
  openshift:
    realm: openshift
storage:
  cache:
    layerinfo: inmemory
  s3:
    accesskey: <key>
    secretkey: <secret>
    region: us-west-2
    bucket: aoe-perf-test
    encrypt: false
    secure: false
    v4auth: true
    rootdirectory: /registry
middleware:
  repository:
    - name: openshift
      options:
        pullthrough: true
2.  Run a build and watch the registry pod's logs


Actual results:

level=error message shown


Expected results:

No errors for normal activity.

Comment 1 Paul Weil 2016-04-26 13:15:31 UTC
Hi Mike.  This is from the docker client and is benign.  The client will periodically attempt to connect without authentication and will receive a 401 from the registry and then resend the attempt with credentials.  It can be ignored.


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