Skip to content

[Failing Test] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container (ci-kubernetes-e2e-ubuntu-gce) #96565

@thejoycekung

Description

@thejoycekung

Which jobs are failing:
ci-kubernetes-e2e-ubuntu-gce

Which test(s) are failing:
[sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container

Since when has it been failing:
Flaking since 9223413...12d9183 Nov 11-12
Failing since 295010c...5cfce4e Nov 12 1PM PST

Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-default

Reason for failure:
Timeout

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/node/pods.go:206
Nov 13 09:51:47.661: timed out waiting for watch events for pod-submit-status-2-1
/usr/local/go/src/runtime/asm_amd64.s:1374

Anything else we need to know:
Example spyglass links:

Can't find a triage link for this test on this job

/sig node
/cc @kubernetes/ci-signal @kubernetes/sig-node-test-failures
/priority important-soon

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.sig/nodeCategorizes an issue or PR as relevant to SIG Node.sig/storageCategorizes an issue or PR as relevant to SIG Storage.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions