[Flake-test] Kubernetes e2e suite: [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]

[aojea]

Kubernetes e2e suite: [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance] expand_less

I start to see this failures on Node tests more often 👀
/retest

Originally posted by @aojea in #109899 (comment)

The error message in the failing job https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/109899/pull-kubernetes-e2e-kind-ipv6/1523605981697675264

<*errors.errorString | 0xc002caa6c0>: {
s: "expected pod "downward-api-9f11f669-8ddf-4af0-a073-700a398e3fbd" success: error while waiting for pod downward-api-5539/downward-api-9f11f669-8ddf-4af0-a073-700a398e3fbd to be Succeeded or Failed: pod "downward-api-9f11f669-8ddf-4af0-a073-700a398e3fbd" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-05-09 10:29:10 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-05-09 10:29:10 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [dapi-container]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-05-09 10:29:10 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [dapi-container]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-05-09 10:29:10 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:fc00:f853:ccd:e793::3 PodIP:fd00:10:244:1::2b PodIPs:[{IP:fd00:10:244:1::2b}] StartTime:2022-05-09 10:29:10 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:dapi-container State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:128,Signal:0,Reason:StartError,Message:failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: failed to write 8755: write /sys/fs/cgroup/rdma/kubelet/kubepods/burstable/podf27330a7-8786-4d5a-bcdd-a7f84e8ac494/02aac26fbb4b6cc0f0aa4c0f1968f19e92a96f5ba572fb8259a10097fb9b6143/cgroup.procs: no such device: unknown,StartedAt:1970-01-01 00:00:00 +0000 UTC,FinishedAt:2022-05-09 10:29:13 +0000 UTC,ContainerID:containerd://02aac26fbb4b6cc0f0aa4c0f1968f19e92a96f5ba572fb8259a10097fb9b6143,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:k8s.gcr.io/e2e-test-images/busybox:1.29-2 ImageID:k8s.gcr.io/e2e-test-images/busybox@sha256:c318242786b139d18676b1c09a0ad7f15fc17f8f16a5b2e625cd0dc8c9703daf ContainerID:containerd://02aac26fbb4b6cc0f0aa4c0f1968f19e92a96f5ba572fb8259a10097fb9b6143 Started:0xc003d1b35a}] QOSClass:Burstable EphemeralContainerStatuses:[]}",

[k8s-ci-robot]

@aojea: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@aojea: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aojea]

/close
duplicate of #109182

[k8s-ci-robot]

@aojea: Closing this issue.

In response to this:

/close
duplicate of #109182

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.