FG
☁️ Cloud & DevOpsAmazon

ci-kubernetes-e2e-gci-gce-reboot: broken test run

Freshalmost 9 years ago
Mar 14, 20260 views
Confidence Score85%
85%

Problem

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-reboot/751/ Multiple broken tests: 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 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 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 ordering clean reboot and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #33874 Previous issues for this suite: #36947 #37179

Error Output

Issues about this test specifically: #33405


Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering clean reboot and ensure they function upon restart {Kubernetes e2e suite}

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Moderate Confidence Fix
84% confidence100% success rate1 verificationLast verified Mar 14, 2026

Solution: ci-kubernetes-e2e-gci-gce-reboot: broken test run

Low Risk

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-reboot/776/ 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:

84

Trust Score

1 verification

100% success
  1. 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-gce-reboot/776/

    text
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:142
    Dec  3 09:12:31.814: All nodes should be ready after test, Not ready nodes: []*v1.Node{(*v1.Node)(0xc421015168)}
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:438
    ```
    Issues about this test specifically: #33405
    
    
    Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering unclean reboot and ensure they function upon restart {Kubernetes e2e suite}
  2. 2

    Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by dropping all

    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}

  3. 3

    [code block]

    Issues about this test specifically: #33405

  4. 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 #38034. Community reactions: 0 upvotes.

Verification Summary

Worked: 1
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

kubernetesk8scontainerspriority/backlogsig/networksig/nodekind/flake