Issue

• We are experiencing a problem with OpenShift where some builds are stuck in "New" status despite the fact that the build has completed successfully and the pod has been deployed and is running.

• For example, the cakephp-example-1 build below is in New status whilst the cakephp-example-1-build pod has completed and the cakephp-example-1-f33f6 pod is running:

  $ oc get all
  NAME                 TYPE      FROM      LATEST
  bc/cakephp-example   Source    Git       1
  
  NAME                       TYPE      FROM          STATUS    STARTED   DURATION
  builds/cakephp-example-1   Source    Git@cd064e5   New                 
  
  NAME                 DOCKER REPO                                                 TAGS      UPDATED
  is/cakephp-example   docker-registry.default.svc:5000/test/cakephp-example   latest    About a minute ago
  
  NAME                 REVISION   DESIRED   CURRENT   TRIGGERED BY
  dc/cakephp-example   1          1         1         config,image(cakephp-example:latest)
  
  NAME                   DESIRED   CURRENT   READY     AGE
  rc/cakephp-example-1   1         1         1         1m
  
  NAME                     HOST/PORT                                                             PATH      SERVICES          PORT      TERMINATION   WILDCARD
  routes/cakephp-example   cakephp-example-test.apps.example.com             cakephp-example   <all>                   None
  
  NAME                  CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
  svc/cakephp-example   172.30.117.135   <none>        8080/TCP   7m
  
  NAME                         READY     STATUS      RESTARTS   AGE
  po/cakephp-example-1-build   0/1       Completed   0          7m
  po/cakephp-example-1-f33f6   1/1       Running     0          1m