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] Etcd failure [Disruptive] should recover from SIGKILL {Kubernetes e2e suite} #29444

Closed
k8s-github-robot opened this issue Jul 22, 2016 · 8 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Milestone

Comments

@k8s-github-robot
Copy link

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}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/etcd_failure.go:66
Expected error:
    <*errors.errorString | 0xc820079fc0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Jul 22, 2016
@k8s-github-robot
Copy link
Author

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}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/etcd_failure.go:66
Jul 27 11:52:38.735: Did not get expected responses within the timeout period of 120.00 seconds.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @pmorie

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

1 similar comment
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @pmorie

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

@k8s-github-robot
Copy link
Author

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}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/etcd_failure.go:66
Sep  3 00:51:07.298: Did not get expected responses within the timeout period of 120.00 seconds.
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rc.go:117

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @pmorie

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

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

[FLAKE-PING] @pmorie

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

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @pmorie

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

@calebamiles calebamiles added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Feb 28, 2017
@calebamiles calebamiles modified the milestone: v1.6 Mar 3, 2017
@deads2k
Copy link
Contributor

deads2k commented Mar 6, 2017

The recent hit is a systemic GKE problem with its own issue here: #37987

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. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

No branches or pull requests

4 participants