Bug 1447386

Summary:	[starter-us-east-1] Builds failing with "Failed to push image: unauthorized"
Product:	OpenShift Online	Reporter:	Mike Fiedler <mifiedle>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED DUPLICATE	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.x	CC:	aos-bugs, bingli, dakini, dmcphers, mfojtik, mifiedle, xtian
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-19 20:28:40 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:

Description Mike Fiedler 2017-05-02 15:14:26 UTC

Description of problem:

Signed up for starter-us-east-1 today and first build in a new project failed with the "unauthorized push" error.

As an end user, it is not at all clear what I should do to recover.

Downloaded: https://repo1.maven.org/maven2/com/google/guava/guava/11.0.2/guava-11.0.2.jar (1610 KB at 1939.2 KB/sec)
[INFO] Including io.undertow:undertow-core:jar:1.3.25.Final-redhat-1 in the shaded jar.
[INFO] Including org.jboss.logging:jboss-logging:jar:3.2.1.Final in the shaded jar.
[INFO] Including org.jboss.xnio:xnio-api:jar:3.3.6.Final in the shaded jar.
[INFO] Including org.jboss.xnio:xnio-nio:jar:3.3.6.Final in the shaded jar.
[INFO] Including io.undertow:undertow-servlet:jar:1.3.25.Final-redhat-1 in the shaded jar.
[INFO] Including org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final in the shaded jar.
[INFO] Including org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final in the shaded jar.
[INFO] Including org.jboss.logmanager:jboss-logmanager:jar:2.0.3.Final-redhat-1 in the shaded jar.
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing /tmp/src/target/undertow-servlet.jar with /tmp/src/target/servlet-1.0.0.Final-shaded.jar
[INFO] Dependency-reduced POM written at: /tmp/src/dependency-reduced-pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22.304 s
[INFO] Finished at: 2017-05-02T15:02:09+00:00
[INFO] Final Memory: 18M/105M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "openshift" could not be activated because it does not exist.
Copying Maven artifacts from /tmp/src/target to /deployments ...
Running: cp *.jar /deployments
... done

Pushing image 172.30.208.107:5000/mffiedler/mff-java:latest ...
error: build error: Failed to push image: unauthorized: authentication required



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

How reproducible:  unknown


Steps to Reproduce:
1. Sign up for an account at api.starter-us-east-1.openshift.com
2. Create a new project
3. Create a new OpenJDK project


Actual results:

Build fails to push image

Expected results:

Build succeeds

Additional info:

Comment 1 Michal Fojtik 2017-05-25 11:34:43 UTC

Seems duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1439614 ?

Comment 3 Mike Fiedler 2017-06-01 13:09:59 UTC

Clearing needinfo

Comment 4 Oleg Bulatov 2017-06-13 12:13:31 UTC

No, in this bug Docker uses `172.30.208.107:5000`, and bug 1439614 applies only to registries on the default port (443 for https, 80 for http).

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

*** Bug 1458950 has been marked as a duplicate of this bug. ***

Comment 6 Stefanie Forrester 2017-06-19 20:28:40 UTC

This is the same thing we're looking at in bz #1462542. The first build is failing to push every time. The workaround is to wait 5 minutes after the project has been created and then try the build again. The second build+push is always successful since the cluster will create the dockercfg secret after the project has existed for about 4 minutes.

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