What were you trying to do that didn't work?

There are a few upstream Kubernetes tests that are flaky on OCP. We’re comparing the results and noticed that in upstream Kubernetes CI they are running ** runc 1.3.0, while OCP is still on runc 1.2.4.

To properly bisect this problem, we need to ensure we’re using the same settings downstream. One step is updating to runc 1.3.1 (the latest version), since the same tests are not flaky upstream.

This way, we can work on de-flaking downstream tests step by step and make sure we are comparing apples to apples, rather than apples to oranges.

What is the impact of this issue to you?

It will block the 4.20 OCP release

Please provide the package NVR for which the bug is seen:

I don't have the reproducer but here's the OCP bug: https://issues.redhat.com/browse/OCPBUGS-61220

How reproducible is this bug?:

Steps to reproduce

Expected results

Actual results