Bug 1458950 - Building failing to push to registry
Summary: Building failing to push to registry
Keywords:
Status: CLOSED DUPLICATE of bug 1447386
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image Registry
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Oleg Bulatov
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-05 22:19 UTC by Dan McPherson
Modified: 2017-06-13 12:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-13 12:14:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan McPherson 2017-06-05 22:19:49 UTC
Description of problem:

I ran 5 builds and all failed with:

Pushing image 172.30.208.107:5000/danmcp/myrubyapp:latest ... error: build error: Failed to push image: unauthorized: authentication required

The 5 failed builds ended up on these 2 nodes:

ip-172-31-62-93.ec2.internal/172.31.62.93
ip-172-31-49-220.ec2.internal/172.31.49.220

The 6th build worked on:

ip-172-31-62-93.ec2.internal/172.31.62.93


There is some guess that this could be related to:


https://bugzilla.redhat.com/show_bug.cgi?id=1422511


But I would be surprised if a node would have recovered from the issue enough to push 1 build.

The issue does seem somewhat related to what node the build happens on because when it starts failing it fails a lot.  But there are plenty of times you can run 10s of successful builds without hitting the issue.



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


How reproducible:


Steps to Reproduce:
1. Run a build
2.
3.

Actual results:
Fail to push

Expected results:
Successful push

Additional info:
This was with the start tier in us-east-1

Comment 2 Oleg Bulatov 2017-06-13 12:14:46 UTC

*** This bug has been marked as a duplicate of bug 1447386 ***


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