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

[k8s.io] Pods should *not* be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} #29614

Closed
k8s-github-robot opened this issue Jul 26, 2016 · 5 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/11976/

Failed: [k8s.io] Pods should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:128
Jul 26 06:32:01.222: Couldn't delete ns "e2e-tests-pods-zglpr": an error on the server has prevented the request from succeeding (delete namespaces e2e-tests-pods-zglpr)
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @cjcullen

This flaky-test issue would love to have more attention...

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @cjcullen

This flaky-test issue would love to have more attention.

2 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @cjcullen

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @cjcullen

This flaky-test issue would love to have more attention.

@cjcullen
Copy link
Member

cjcullen commented Oct 5, 2016

GKE test stack's flakiness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

2 participants