origin: Build pod not running on cluster created using oc cluster up

I am currently unable to get a host of different applications to get successfully built and deployed on Openshift 3.10 clusters created via oc cluster up. An example application is: https://github.com/snowdrop/spring-boot-http-booster.

The application gets correctly built and deployed on all Openshift 3.9 clusters, as well as “real” (ones that have been created via openshift-ansible) Openshift 3.10 clusters.

I have tried a host of different oc cluster up scenarios (straight up oc cluster up on a linux machine, Minishift, clean CentOS 7 VM) and they all fail.

Version

v3.10.0

Steps To Reproduce

1. Create cluster via oc cluster up
2. Clone application: https://github.com/snowdrop/spring-boot-http-booster
3. ./mvnw fabric8:deploy -Popenshift -DskipTest

Current Result

It seems like the git-clone init container is stuck. The only logs it has are: Receiving source from STDIN as archive

Expected Result

The application should be deployed normally as is the case for all Openshift 3.9 clusters as well as “real” Openshift 3.10 clusters

Additional Information

Starting the build with an increased log level (done manually via oc start-build spring-boot-rest-http-s2i --from-archive=/home/gandrian/projects/redhat/spring-boot-http-booster/target/docker/spring-boot-rest-http/latest/tmp/docker-build.tar --loglevel=5 --build-loglevel=5 -F) doesn’t yield any results. The build does start, but there is nothing in the logs.

Only when I do oc logs spring-boot-rest-http-s2i-5-build do I see Error from server (BadRequest): container "sti-build" in pod "spring-boot-rest-http-s2i-5-build" is waiting to start: PodInitializing.

After some time, the oc start-build responds with:

I0816 19:11:43.745383   20084 helpers.go:201] server response object: [{
  "metadata": {},
  "status": "Failure",
  "message": "unable to wait for build spring-boot-rest-http-s2i-7 to run: timed out waiting for the condition",
  "reason": "BadRequest",
  "code": 400
}]