Skip to content

[Flaking Test][sig-node] Container Runtime blackbox test on terminated container should report termination message from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance] #129760

@stmcginnis

Description

@stmcginnis

Which jobs are flaking?

master-blocking

  • gce-ubuntu-master-containerd

Which tests are flaking?

E2eNode Suite.[It] [sig-node] Container Runtime blackbox test on terminated container should report termination message from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]

Prow
Triage

Since when has it been flaking?

1/10/2025, 6:57:34 PM
1/21/2025, 5:54:07 AM

Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv1-node-e2e-conformance

Reason for failure (if possible)

{ failed [FAILED] Timed out after 300.001s.
Expected
    <v1.PodPhase>: Failed
to equal
    <v1.PodPhase>: Succeeded
In [It] at: k8s.io/kubernetes/test/e2e/common/node/runtime.go:157 @ 01/21/25 12:18:04.935
}

Anything else we need to know?

N/A

Relevant SIG(s)

/sig node
cc @kubernetes/release-team-release-signal

Metadata

Metadata

Assignees

Labels

kind/flakeCategorizes issue or PR as related to a flaky test.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.sig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Status

RESOLVED

Status

Done

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions