Which jobs are flaking?
master-blocking
- ci-crio-cgroupv2-node-e2e-conformance
- ci-crio-cgroupv1-node-e2e-conformance
Which tests are flaking?
E2eNode Suite.[It] [sig-node] Hostname of Pod [NodeConformance] a pod without FQDN is not affected by SetHostnameAsFQDN field
Triage
Prow ci-crio-cgroupv2-node-e2e-conformance
Prow ci-crio-cgroupv1-node-e2e-conformance
Since when has it been flaking?
5/30/2025, 4:44:00 AM
5/26/2025, 12:02:49 AM
5/22/2025, 9:50:45 AM
5/15/2025, 2:04:14 AM
5/14/2025, 6:59:15 PM
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv2-node-e2e-conformance
Reason for failure (if possible)
{ failed [FAILED] expected pod "hostfqdn-123062" success: Told to stop trying after 2.016s.
pod "hostfqdn-123062" failed with status:
<v1.PodStatus>:
conditions:
- lastProbeTime: null
lastTransitionTime: "2025-05-29T23:35:01Z"
status: "False"
type: PodReadyToStartContainers
- lastProbeTime: null
lastTransitionTime: "2025-05-29T23:34:59Z"
status: "True"
type: Initialized
- lastProbeTime: null
lastTransitionTime: "2025-05-29T23:34:59Z"
reason: PodFailed
status: "False"
type: Ready
- lastProbeTime: null
lastTransitionTime: "2025-05-29T23:34:59Z"
reason: PodFailed
status: "False"
type: ContainersReady
- lastProbeTime: null
lastTransitionTime: "2025-05-29T23:34:59Z"
status: "True"
type: PodScheduled
containerStatuses:
- containerID: cri-o://33443ca914680034b32be4a1e55bc3dbb512a1b4950cc2f7c90f110ed541f9c8
image: registry.k8s.io/e2e-test-images/busybox:1.37.0-1
imageID: registry.k8s.io/e2e-test-images/busybox@sha256:0ffbe172f8d245c83f285c6992b452c53d085661e03ddfd3b484332026e6c8bb
lastState: {}
name: test-container
ready: false
resources: {}
restartCount: 0
started: false
state:
terminated:
containerID: cri-o://33443ca914680034b32be4a1e55bc3dbb512a1b4950cc2f7c90f110ed541f9c8
exitCode: 255
finishedAt: "2025-05-29T23:34:59Z"
reason: Error
startedAt: "2025-05-29T23:34:59Z"
user:
linux:
gid: 0
supplementalGroups:
- 0
- 10
uid: 0
hostIP: 10.138.0.5
hostIPs:
- ip: 10.138.0.5
phase: Failed
podIP: 10.85.0.230
podIPs:
- ip: 10.85.0.230
- ip: 1100:200::e6
qosClass: BestEffort
startTime: "2025-05-29T23:34:59Z"
In [It] at: k8s.io/kubernetes/test/e2e/framework/pod/output/output.go:263 @ 05/29/25 23:35:01.234
}
Anything else we need to know?
N/A
Relevant SIG(s)
/sig node
cc @kubernetes/release-team-release-signal
Which jobs are flaking?
master-blocking
Which tests are flaking?
E2eNode Suite.[It] [sig-node] Hostname of Pod [NodeConformance] a pod without FQDN is not affected by SetHostnameAsFQDN field
Triage
Prow ci-crio-cgroupv2-node-e2e-conformance
Prow ci-crio-cgroupv1-node-e2e-conformance
Since when has it been flaking?
5/30/2025, 4:44:00 AM
5/26/2025, 12:02:49 AM
5/22/2025, 9:50:45 AM
5/15/2025, 2:04:14 AM
5/14/2025, 6:59:15 PM
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv2-node-e2e-conformance
Reason for failure (if possible)
Anything else we need to know?
N/A
Relevant SIG(s)
/sig node
cc @kubernetes/release-team-release-signal