Description of problem: When trying to s2i build from source, the builder took 10 minutes and failed at 82% percent. Previously, this built in under 3 minutes on 3.4.1.8. @Stefanie was able to resolve by increasing replica count to 6. However, we believe this only a quick fix, and not a solution Version-Release number of selected component (if applicable): OpenShift Master: v3.4.1.10 (online version 3.4.1.14) Kubernetes Master: v1.4.0+776c994 How reproducible: Just once before @Stefanie increased the replica count Steps to Reproduce: 1. oc new-app php~https://github.com/wgordon17/openshift.org#deploy --name=test Actual results: Build failed, and the registry push took the longest amount of time Expected results: Build succeeds Additional info: $ oc describe build test-1 Name: test-1 Namespace: wgordon-test Created: 27 minutes ago Labels: app=test buildconfig=test openshift.io/build-config.name=test openshift.io/build.start-policy=Serial Annotations: openshift.io/build-config.name=test openshift.io/build.number=1 openshift.io/build.pod-name=test-1-build Status: Failed Started: Wed, 29 Mar 2017 12:53:12 EDT Duration: 10m47s Build Config: test Build Pod: test-1-build Strategy: Source URL: https://github.com/wgordon17/openshift.org Ref: deploy Commit: f653ceb (Update .htaccess) Author/Committer: Will Gordon / GitHub From Image: DockerImage registry.access.redhat.com/rhscl/php-56-rhel7@sha256:4e937adb6f367ebc0cb18acd15f2614d501584ff586de6e575891a7f455b083b Output to: ImageStreamTag test:latest Push Secret: builder-dockercfg-ghjpu Build trigger cause: Image change Image ID: registry.access.redhat.com/rhscl/php-56-rhel7@sha256:4e937adb6f367ebc0cb18acd15f2614d501584ff586de6e575891a7f455b083b Image Name/Kind: php:5.6 / ImageStreamTag No events. --------------- $ docker pull registry.preview.openshift.com/wgordon-test/test:latest $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE registry.preview.openshift.com/wgordon-test/test latest 3367cb78a7fa 11 minutes ago 512 MB
Looks like this bug hasn't been updated for awhile, and might just be a network or disk issue that has been resolved in the meantime? Do you still encounter this problem?