Skip to content

should check if kubectl describe prints relevant information for rc and pods - flake #9825

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

Closed
bparees opened this issue Jul 13, 2016 · 1 comment
Assignees
Labels
component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2

Comments

@bparees
Copy link
Contributor

bparees commented Jul 13, 2016


[k8s.io] Kubectl client
/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:685
  [k8s.io] Kubectl describe
  /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:685
    should check if kubectl describe prints relevant information for rc and pods [Conformance] [It]
    /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/kubectl.go:583

    Jul 13 14:36:55.722: Verified 0 of 1 pods , error : timed out waiting for the condition

    /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/kubectl.go:192

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/3403/consoleFull

@ncdc
Copy link
Contributor

ncdc commented Jul 15, 2016

@Kargakis would you mind triaging this to try to figure out why it didn't get a pod? I'm guessing it's related to the slow secret mounting/unmounting.

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

No branches or pull requests

4 participants