FG
☁️ Cloud & DevOpsAmazon

kubernetes-e2e-kops-aws-updown: broken test run

Freshover 9 years ago
Mar 14, 20260 views
Confidence Score86%
86%

Problem

Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-kops-aws-updown/2102/ Run so broken it didn't make JUnit output!

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-kops-aws-updown: broken test run

Low Risk

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-kops-aws-updown/2821/ Multiple broken tests: Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should function for intra-pod communication: http [Conformance] {Kubernetes e2e suite} [code block] Issues about this test specifically: #32375 Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should f

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-kops-aws-updown/2821/

    text
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/networking.go:38
    Oct 18 16:38:51.869: Failed to find expected endpoints:
    Tries 0
    Command curl -q -s 'http://100.96.2.7:8080/dial?request=hostName&protocol=http&host=10.123.45.5&port=8080&tries=1'
    retrieved map[]
    expected map[netserver-2:{}]
    
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/networking_utils.go:206
    ```
    
    Issues about this test specifically: #32375
    
    Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should function for node-pod communication: udp [Conformance] {Kubernetes e2e suite}
  2. 2

    Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should function for i

    Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should function for intra-pod communication: http [Conformance] {Kubernetes e2e suite}

  3. 3

    Issues about this test specifically: #32375

    Issues about this test specifically: #32375

  4. 4

    Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should function for n

    Failed: [k8s.io] Networking [k8s.io] Granular Checks: Pods should function for node-pod communication: udp [Conformance] {Kubernetes e2e suite}

Validation

Resolved in kubernetes/kubernetes GitHub issue #34865. 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-urgentkind/flake