should include various info in status [Conformance] [It]

[0xmichalis]

• Failure [307.080 seconds]
deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:767
  with enhanced status
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:347
    should include various info in status [Conformance] [It]
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:346

    Expected error:
        <*errors.errorString | 0xc8200f5600>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    not to have occurred

    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:328
------------------------------

Seems that the deployment pods couldn't come up, resulting in the deployer timing out:

Oct  7 00:59:14.411: INFO: At 2016-10-07 00:54:19 -0400 EDT - event for deployment-simple-1-89t2i: {kubelet 172.18.1.159} FailedSync: Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: An error occurred trying to connect: Post http://%2Fvar%2Frun%2Fdocker.sock/containers/create?name=k8s_POD.ca35dcd0_deployment-simple-1-89t2i_extended-test-cli-deployment-5noet-f4xon_19ace84f-8c4a-11e6-946d-0ed616a35903_0c542bd2: EOF"

Oct  7 00:59:14.411: INFO: At 2016-10-07 00:54:19 -0400 EDT - event for deployment-simple-1-jn16b: {kubelet 172.18.1.159} FailedSync: Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "InspectContainer: Cannot connect to the Docker daemon. Is the docker daemon running on this host?"

Oct  7 00:59:14.097: INFO: Running 'oc logs --namespace=extended-test-cli-deployment-5noet-f4xon --config=/tmp/extended-test-cli-deployment-5noet-f4xon-user.kubeconfig pod/deployment-simple-1-deploy'
Oct  7 00:59:14.397: INFO: --- pod deployment-simple-1-deploy logs
--> Scaling deployment-simple-1 to 2
--> Waiting up to 10m0s for pods in deployment deployment-simple-1 to become ready---

[0xmichalis]

Same fixture used as #11257

@mfojtik we should stop using that image

[mfojtik]

@Kargakis that image s 6MB scratch that has just golang http server inside...

[mfojtik]

@Kargakis but we can switch to something we already have on node and instead of http readiness do exec

[0xmichalis]

The problem is not the size of the image. It seems that it fails the readiness probe randomly. Locally I can always see one of the two pods hanging as unready but I am not sure why it happens.

[mfojtik]

@Kargakis #11261

[mfojtik]

@Kargakis maybe the http server that we have inside that image is using some weak code