Description of problem:

Recent 4.12 CI jobs are failing upgrade jobs with errors like:

{  fail [k8s.io/kubernetes@v1.25.0/test/e2e/common/node/kubelet.go:214]: Timed out after 60.000s.
Expected
    <string>: "time="..."
to equal       |
    <string>: "/bin/s..."
Ginkgo exit error 1: exit with code 1}

Version-Release number of selected component (if applicable):

Failures started in 4.12.0-0.ci-2023-04-23-083446

This build bumped RHCOS from 412.86.202304191831-0 to 412.86.202304211232-0

The diff shows that runc got upgraded (no other changes) from runc-3-1.1.4-2.rhaos4.12.el8-x86_64 to runc-3-1.1.6-1.rhaos4.12.el8-x86_64

How reproducible:

Always, 4.12 upgrade CI appears to be blocked by this

Steps to Reproduce:

Observe recently failing 4.12 CI jobs at https://amd64.ocp.releases.ci.openshift.org/#4.12.0-0.ci

Additional info:

Some discussion with kkolyshk on slack indicates this is a result of this fix: https://github.com/opencontainers/runc/pull/3623 - a workaround (add a mount point for /sys into the impacted containers) was mentioned, but I suspect we may just want to revert the RHCOS bump pending resolution of this instead?