☁️ Cloud & DevOpsAmazon

[k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite}

Freshover 9 years ago

Mar 14, 20260 views

Confidence Score87%

87%

Problem

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-prod-parallel/2086/ Failed: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite} [code block]

Unverified for your environment

Select your OS to check compatibility.

Your OS

OS version

Product version

1 Fix

Canonical Fix

Moderate Confidence Fix

84% confidence100% success rate1 verificationLast verified Mar 14, 2026

Solution: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite}

Low Risk

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/11068/ Failed: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite} [code block]

Trust Score

1 verification

100% success

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

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/11068/

text

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kube_proxy.go:204
Expected
    <float64>: 3542
to be <
    <int>: 10
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kube_proxy.go:203

2
Failed: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite
Failed: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite}

Validation

Resolved in kubernetes/kubernetes GitHub issue #36288. Community reactions: 0 upvotes.

Verification Summary

Worked: 1

Last verified Mar 14, 2026

Environment

Submitted by

Alex Chen

2450 rep