-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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] Etcd failure [Disruptive] should recover from SIGKILL {Kubernetes e2e suite} #29444
Comments
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1806/ Failed: [k8s.io] Etcd failure [Disruptive] should recover from SIGKILL {Kubernetes e2e suite}
|
[FLAKE-PING] @pmorie This flaky-test issue would love to have more attention... |
1 similar comment
[FLAKE-PING] @pmorie This flaky-test issue would love to have more attention... |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/2070/ Failed: [k8s.io] Etcd failure [Disruptive] should recover from SIGKILL {Kubernetes e2e suite}
|
[FLAKE-PING] @pmorie This flaky-test issue would love to have more attention. |
2 similar comments
[FLAKE-PING] @pmorie This flaky-test issue would love to have more attention. |
[FLAKE-PING] @pmorie This flaky-test issue would love to have more attention. |
The recent hit is a systemic GKE problem with its own issue here: #37987 |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1767/
Failed: [k8s.io] Etcd failure [Disruptive] should recover from SIGKILL {Kubernetes e2e suite}
The text was updated successfully, but these errors were encountered: