Extended.deploymentconfigs with custom deployments [Conformance] should run the custom deployment steps

[bparees]

• Failure [27.036 seconds]
deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:309
  with custom deployments
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:211
    should run the custom deployment steps [Conformance] [It]
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:210

    Expected
        <string>: --> pre: Running hook pod ...
        test pre hook executed
        --> pre: Success
        --> Scaling custom-deployment-1 to 2
        --> Waiting up to 10m0s for pods in deployment custom-deployment-1 to become ready
        --> Reached 50%
        Halfway
        --> pre: Hook pod already succeeded
        --> Waiting up to 10m0s for pods in deployment custom-deployment-1 to become ready
    to contain substring
        <string>: Finished

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

as seen here: https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/1925/consoleFull

[smarterclayton]

@stevekuznetsov is this a similar symptom to the Docker 1.10 hangs?

[stevekuznetsov]

Node never becomes unresponsive, very unlikely it's the same cause.

[0xmichalis]

One more instance in https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/5578/consoleFull

The deployment is successful which means the deployer pod was Complete.

apiVersion: v1
kind: ReplicationController
metadata:
  annotations:
    openshift.io/deployer-pod.name: custom-deployment-1-deploy
    openshift.io/deployment-config.latest-version: "1"
    openshift.io/deployment-config.name: custom-deployment
    openshift.io/deployment.phase: Complete

Not sure why we cannot get all the logs though...

[0xmichalis]

Hm this is slightly different:

Expected
        <string>: --> pre: Running hook pod ...
        test pre hook executed
        --> pre: Success
        --> Scaling custom-deployment-1 to 2
        --> Waiting up to 10m0s for pods in deployment custom-deployment-1 to become ready
        --> Reached 50%
        Halfway
        --> pre: Hook pod already succeeded
        --> Waiting up to 10m0s for pods in deployment custom-deployment-1 to become ready
        --> Success
    to contain substring
        <string>: Finished

Finished should come before --> Success but it's somehow lost?

[smarterclayton]

Very strange - race in pod log lookups?

On Thu, Aug 25, 2016 at 9:44 AM, Michail Kargakis [email protected]
wrote:

Hm this is slightly different:

Expected
: --> pre: Running hook pod ...
test pre hook executed
--> pre: Success
--> Scaling custom-deployment-1 to 2
--> Waiting up to 10m0s for pods in deployment custom-deployment-1 to become ready
--> Reached 50%
Halfway
--> pre: Hook pod already succeeded
--> Waiting up to 10m0s for pods in deployment custom-deployment-1 to become ready
--> Success
to contain substring
: Finished

Finished should come before --> Success but it's somehow lost?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#9285 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_p3TLdnuCwYNMF2JwoqKofLMc4Ai_ks5qjZxAgaJpZM4IzcRC
.

[ncdc]

Possible fix: projectatomic/docker#218

[bparees]

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/151/

[ncdc]

This sure sounds like it might be journal rate limiting, maybe?

[ncdc]

cc @soltysh

[soltysh]

#12558 is still open and I'm still trying to figure it out. So there's a chance when I increase the limits in journal this will be solve along with it.

[mfojtik]

Closing this due to age and that we have #14785, #14140, #13980 which basically tracks the same issue with journald rate limiting.