Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extended.deploymentconfigs with minimum ready seconds set [Conformance] should not transition the deployment to Complete before satisfied #11873

Closed
bparees opened this issue Nov 10, 2016 · 6 comments
Assignees
Labels
component/apps kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2

Comments

@bparees
Copy link
Contributor

bparees commented Nov 10, 2016

deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:840
  with minimum ready seconds set [Conformance] [AfterEach]
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:799
    should not transition the deployment to Complete before satisfied
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:798

    Nov 10 10:59:42.156: Couldn't delete ns: "extended-test-cli-deployment-1m1y0-wpn5h": namespace extended-test-cli-deployment-1m1y0-wpn5h was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace extended-test-cli-deployment-1m1y0-wpn5h was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"})

    /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:338
@mfojtik
Copy link
Contributor

mfojtik commented Nov 11, 2016

@bparees do you have link to Jenkins for this one?

It seems like the Kube finalizers took longer time than usual to complete which I think is pretty rare. Bumping to P2.

@bparees
Copy link
Contributor Author

bparees commented Nov 11, 2016

no, sorry i forgot to include it.

@0xmichalis
Copy link
Contributor

Seems like another instance of #10670

@legionus
Copy link
Contributor

#11925

@0xmichalis
Copy link
Contributor

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/8748/consoleFull#-169259343956c60d7be4b02b88ae8c268b

Nov 18 13:18:45.374: INFO: Running 'oc logs --config=/tmp/extended-test-cli-deployment-fmn4r-h66y4-user.kubeconfig --namespace=extended-test-cli-deployment-fmn4r-h66y4 pod/minreadytest-1-deploy --timestamps=true'
Nov 18 13:18:45.668: INFO: --- pod minreadytest-1-deploy logs
2016-11-18T18:17:44.020346000Z --> Scaling minreadytest-1 to 2
2016-11-18T18:17:44.116248000Z --> Waiting up to 10m0s for pods in deployment minreadytest-1 to become ready---
• Failure [177.617 seconds]
deploymentconfigs
/data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:840
  with minimum ready seconds set [Conformance]
  /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:799
    should not transition the deployment to Complete before satisfied [It]
    /data/src/github.com/openshift/origin/test/extended/deployments/deployments.go:798

    Expected error:
        <*errors.errorString | 0xc82090cdf0>: {
            s: "deployment config \"minreadytest\" never became ready (ready: 0, desired: 2)",
        }
        deployment config "minreadytest" never became ready (ready: 0, desired: 2)
    not to have occurred

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

@bparees
Copy link
Contributor Author

bparees commented Dec 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/apps kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2
Projects
None yet
Development

No branches or pull requests

5 participants