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

GCE reboot tests flaky #14772

Closed
fabioy opened this issue Sep 29, 2015 · 4 comments
Closed

GCE reboot tests flaky #14772

fabioy opened this issue Sep 29, 2015 · 4 comments
Assignees
Labels
area/test area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@fabioy
Copy link
Contributor

fabioy commented Sep 29, 2015

A few reboot tests are being flaky, affecting the Jenkins project status, which affects the merge-bot rate. The flaky tests:

(2 fails in last 10 runs)

  • Reboot each node by switching off the network interface and ensure they function upon switch on
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:83
    Sep 29 10:10:46.304: Node e2e-reboot-minion-5vaz failed reboot test.

(2 fails in last 10 runs)

  • Reboot each node by ordering unclean reboot and ensure they function upon restart
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:71
    Sep 29 10:12:59.060: Node e2e-reboot-minion-i0rp failed reboot test.

(2 fails in last 10 runs)
-Reboot each node by dropping all outbound packets for a while and ensure they function afterwards
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:99
Sep 29 12:58:18.443: Node e2e-reboot-minion-cm4k failed reboot test.

(1 fail in last 10 runs)
-Reboot each node by triggering kernel panic and ensure they function upon restart
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:77
Sep 29 14:18:47.006: Node e2e-reboot-minion-jx2o failed reboot test.

@fabioy fabioy added help-wanted area/test priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels Sep 29, 2015
@brendandburns
Copy link
Contributor

@davidopp for triage

@bgrant0607
Copy link
Member

See also #9349, #12800

@ghost
Copy link

ghost commented Sep 30, 2015

Close once we've seen 20 successful test runs after merging #14784, which hopefully addresses the flakyness reported here.

@ghost
Copy link

ghost commented Oct 2, 2015

Success!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

3 participants