11.3% of 4.7 runs (not occurring before 4.7) have this error in them ns/openshift-cluster-node-tuning-operator pod/tuned-qrk7b node/ip-10-0-201-77.us-east-2.compute.internal - never deleted - reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to pin namespaces [uts]: [pinns:e]: /var/run/utsns exists and is not a directory: File exists example job https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.7/1355501971028578304 Looks like we introduced a new race condition in this namespace and it impacts pod stop SLOs. Must fix for 4.7 because of the prevalence of the regression.
should be fixed in attached version (not sure, I haven't personally reproduced)
Today we have 47.83.202102031754-0 in https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/releasestream/4.7.0-0.ci/release/4.7.0-0.ci-2021-02-08-221831 (https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.7/1358904576626921472/build-log.txt) Tomorrow's build should have d 47.83.202102040111-0 or later. Waiting to check on this
All of the failures here: https://search.ci.openshift.org/?search=failed+to+pin+namespaces&maxAge=48h&context=1&type=bug%2Bjunit&name=4.7&maxMatches=5&maxBytes=20971520&groupBy=job seem to be 4.9 (which I inspected and has an old version of cri-o 1.20 that doesn't have the fixes needed I believe this is fixed in 4.7
no long see the failures in above CI jobs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438