FG
☁️ Cloud & DevOpsAmazon

kubernetes-e2e-gci-gke-flaky: broken test run

Freshover 9 years ago
Mar 14, 20260 views
Confidence Score89%
89%

Problem

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-flaky/31/ Multiple broken tests: Failed: [k8s.io] NodeOutOfDisk [Serial] [Flaky] [Disruptive] runs out of disk space {Kubernetes e2e suite} [code block] Failed: [k8s.io] PersistentVolumes create a PV and a pre-bound PVC: test write access [Flaky] {Kubernetes e2e suite} [code block] Failed: [k8s.io] PersistentVolumes create a PVC and a pre-bound PV: test write access [Flaky] {Kubernetes e2e suite} [code block] Failed: Test {e2e.go} [code block] Issues about this test specifically: #33361 Failed: [k8s.io] PersistentVolumes create a PVC and non-pre-bound PV: test write access [Flaky] {Kubernetes e2e suite} [code block] Failed: [k8s.io] PersistentVolumes should create a non-pre-bound PV and PVC: test write access [Flaky] {Kubernetes e2e suite} [code block]

Error Output

error running Ginkgo tests: exit status 1

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: kubernetes-e2e-gci-gke-flaky: broken test run

Low Risk

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-flaky/32/ Multiple broken tests: Failed: [k8s.io] PersistentVolumes should create a non-pre-bound PV and PVC: test write access [Flaky] {Kubernetes e2e suite} [code block] Failed: [k8s.io] PersistentVolumes create a PV and a pre-bound PVC: test write access [Flaky] {Kubernetes e2e suite} [code block] Fail

84

Trust Score

1 verification

100% success
  1. 1

    https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-

    https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-flaky/32/

    text
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/persistent_volumes.go:486
    Sep 23 11:08:04.390: Pod write-pod-xt01a exited with non-zero exitcode: Pod write-pod-xt01a returned non-zero exitcode: gave up waiting for pod 'write-pod-xt01a' to be 'success or failure' after 5m0s
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/persistent_volumes.go:484
    ```
    
    Failed: [k8s.io] PersistentVolumes create a PV and a pre-bound PVC: test write access [Flaky] {Kubernetes e2e suite}
  2. 2

    Failed: [k8s.io] PersistentVolumes should create a non-pre-bound PV and PVC: tes

    Failed: [k8s.io] PersistentVolumes should create a non-pre-bound PV and PVC: test write access [Flaky] {Kubernetes e2e suite}

  3. 3

    Failed: [k8s.io] PersistentVolumes create a PV and a pre-bound PVC: test write a

    Failed: [k8s.io] PersistentVolumes create a PV and a pre-bound PVC: test write access [Flaky] {Kubernetes e2e suite}

  4. 4

    Issues about this test specifically: #33361

    Issues about this test specifically: #33361

Validation

Resolved in kubernetes/kubernetes GitHub issue #33401. 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/critical-urgentarea/test-infrakind/flake