Bug 1370930 - Build fails after git push
Summary: Build fails after git push
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Build
Version: 3.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Stefanie Forrester
QA Contact: Wang Haoran
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-28 14:21 UTC by bugreport398
Modified: 2016-09-01 16:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-01 16:37:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description bugreport398 2016-08-28 14:21:25 UTC
Description of problem:

First time this I have seen this happen, but build is failing after git push on python 2.7 application.

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

Dev preview

How reproducible:

I don't know.

Steps to Reproduce:

1. Do a git push on python 2.7 application
2. Watch build progress in console.  
3. See something like: "Build python-app #43 failed. View Log | Dismiss"
4. Try and "rebuild", get same error message.  

Actual results:

Build python-app #43 failed. View Log | Dismiss

Expected results:

Build, deploy and scale occurs after git push.  

Additional info:

Last part of error logs:

I0828 10:09:01.417159       1 sti.go:334] Successfully built my-app/python-app-42:8f4d2b5d
I0828 10:09:01.455404       1 cleanup.go:23] Removing temporary directory /tmp/s2i-build195801070
I0828 10:09:01.455429       1 fs.go:156] Removing directory '/tmp/s2i-build195801070'
I0828 10:09:01.529446       1 sti.go:268] Using provided push secret for pushing 172.30.30.43:5000/my-app/python-app:latest image
I0828 10:09:01.529478       1 sti.go:272] Pushing 172.30.30.43:5000/my-app/python-app:latest image ...
E0828 10:09:01.672606       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
E0828 10:09:06.751858       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
E0828 10:09:11.823631       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
E0828 10:09:16.883281       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
E0828 10:09:21.957326       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
E0828 10:09:27.027646       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
E0828 10:09:32.099938       1 dockerutil.go:86] push for image 172.30.30.43:5000/my-app/python-app:latest failed, will retry in 5s ...
I0828 10:09:37.100249       1 sti.go:277] Registry server Address: 
I0828 10:09:37.100281       1 sti.go:278] Registry server User Name: serviceaccount
I0828 10:09:37.100289       1 sti.go:279] Registry server Email: serviceaccount
I0828 10:09:37.100296       1 sti.go:284] Registry server Password: <<non-empty>>
F0828 10:09:37.100306       1 builder.go:204] Error: build error: Failed to push image. Response from registry is: unable to ping registry endpoint https://172.30.30.43:5000/v0/
v2 ping attempt failed with error: Get https://172.30.30.43:5000/v2/: x509: certificate signed by unknown authority
v1 ping attempt failed with error: Get https://172.30.30.43:5000/v1/_ping: x509: certificate signed by unknown authority

Comment 1 Cesar Wong 2016-08-29 14:25:26 UTC
It seems that at least one node is not configured with the right --insecure-registry argument.

Comment 2 Stefanie Forrester 2016-08-29 23:07:07 UTC
The registry IP listed above doesn't match any of the Dev Preview INT/STG/PROD environments. Can you tell me the address of the web console you're using? That'll help me find the right cluster.

For example, https://console.preview.openshift.com/console/

Comment 3 bugreport398 2016-09-01 11:55:05 UTC
Apologies for late reply, but I always access through:

https://console.hackathon.openshift.com/console/

Comment 4 bugreport398 2016-09-01 11:56:05 UTC
But building is occurring normally now.

Comment 5 Stefanie Forrester 2016-09-01 16:37:34 UTC
Ah, that cluster. That makes sense. There was an issue with the docker certs on some new nodes, but it has been resolved.


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