Skip to content

Failure cluster [34ae9536...] [sig-node] [sig-windows] Container runtime failed test #128934

@esotsal

Description

@esotsal

Failure cluster 34ae95361eb5abbcb926

image

Error text:
[FAILED] Timed out after 300.000s.
Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
In [It] at: k8s.io/kubernetes/test/e2e/common/node/runtime.go:157 @ 11/13/24 11:24:41.726

Recent failures:

11/22/2024, 4:01:07 AM ci-kubernetes-e2e-windows-containerd-gce-master
11/22/2024, 3:14:07 AM ci-kubernetes-e2e-windows-win2022-containerd-gce-master
11/21/2024, 11:14:03 PM ci-kubernetes-e2e-windows-win2022-containerd-gce-master
11/21/2024, 8:00:04 PM ci-kubernetes-e2e-windows-containerd-gce-master
11/21/2024, 7:14:04 PM ci-kubernetes-e2e-windows-win2022-containerd-gce-master

/kind failing-test
/kind flake

Flake > 65% occurrence

/sig node
/sig windows

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.kind/flakeCategorizes issue or PR as related to a flaky test.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/nodeCategorizes an issue or PR as relevant to SIG Node.sig/windowsCategorizes an issue or PR as relevant to SIG Windows.

    Type

    No type

    Projects

    Status

    Done

    Status

    Archive-it

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions