ci-kubernetes-e2e-gci-gke-reboot: broken test run
Problem
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke-reboot/346/ Multiple broken tests: Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by dropping all inbound packets for a while and ensure they function afterwards {Kubernetes e2e suite} [code block] Issues about this test specifically: #33405 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on {Kubernetes e2e suite} [code block] Issues about this test specifically: #33407 #33623 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering clean reboot and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #33874 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering unclean reboot and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #33882 #35316 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by dropping all outbound packets for a while and ensure they function afterwards {Kubernetes e2e suite} [code block] Issues about this test specifically: #33703 #36230 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by triggering kernel panic and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #34123 #35398 Previous issues for this suite: #37
Error Output
Issues about this test specifically: #33874
Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering unclean reboot and ensure they function upon restart {Kubernetes e2e suite}Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: ci-kubernetes-e2e-gci-gke-reboot: broken test run
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke-reboot/351/ Multiple broken tests: Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by triggering kernel panic and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #34123 #35398 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot]
Trust Score
1 verification
- 1
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke-reboot/351/
text/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:106 Dec 2 00:40:31.745: Test failed; at least one node failed to reboot in the time given. /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:170 ``` Issues about this test specifically: #34123 #35398 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering unclean reboot and ensure they function upon restart {Kubernetes e2e suite} ``` /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:100 Dec 2 00:50:44.958: Test failed; at least one node failed to reboot in the time given. /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/reboot.go:170 - 2
Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by triggering ke
Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by triggering kernel panic and ensure they function upon restart {Kubernetes e2e suite}
- 3
[code block]
Issues about this test specifically: #34123 #35398
- 4
Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering uncl
Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering unclean reboot and ensure they function upon restart {Kubernetes e2e suite}
Validation
Resolved in kubernetes/kubernetes GitHub issue #37915. Community reactions: 0 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep