[Flaky] Kubernetes e2e suite: [sig-node] Pods Extended Pod Container Status should never report container start when an init container fails

[sanposhiho]

Which jobs are flaking?

pull-kubernetes-e2e-kind

Which tests are flaking?

Kubernetes e2e suite: [sig-node] Pods Extended Pod Container Status should never report container start when an init container fails

Since when has it been flaking?

unknown

Testgrid link

https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-e2e-kind&include-filter-by-regex=Pods\sExtended\sPod\sContainer\sStatus\sshould\snever\sreport\scontainer

Reason for failure (if possible)

{ Failure test/e2e/node/pods.go:216
May  8 05:39:54.739: 1 errors:
pod pod-terminate-status-1-2 on node kind-worker2 container unexpected exit code 128: start=1970-01-01 00:00:00 +0000 UTC end=2022-05-08 05:37:07 +0000 UTC 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 214182: open /sys/fs/cgroup/rdma/kubelet/kubepods/burstable/pod5e8eb68f-bb0f-45af-ad98-a261a657ca29/3a34bba7ea7d41b582908f6acfecab913690f7e224807d98e63519c988ad8e9c/cgroup.procs: no such device: unknown
test/e2e/node/pods.go:218}

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/109832/pull-kubernetes-e2e-kind/1523166127151124480

Anything else we need to know?

No response

Relevant SIG(s)

/sig node

[k8s-ci-robot]

@sanposhiho: 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.

[sanposhiho]

seems duplicated with #109182

/close

[k8s-ci-robot]

@sanposhiho: Closing this issue.

In response to this:

seems duplicated with #109182

/close

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.