Description of problem:
Currently, openshift and upstream CRI-O diverge on their recommendation for crio wipe. upstream users have reported confusion at the enabling of crio wipe by default, but it is vital to the health of self upgrading openshift.
At present, the crio config field for crio wipe is not configured by the MCO. this has worked fine, but the upstream plans on changing the default to allow upstream users to continue to not have it enabled by default. as such, it should be pinned in MCO
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cat /etc/crio/crio.conf.d/* | grep version_file_persist
should contain /var/lib/crio/version
Verified on 4.10.0-0.nightly-2021-10-25-190146
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.10.0-0.nightly-2021-10-25-190146 True False 3h49m Cluster version is 4.10.0-0.nightly-2021-10-25-190146
$ oc get nodes
NAME STATUS ROLES AGE VERSION
ip-10-0-156-16.us-east-2.compute.internal Ready worker 3h59m v1.22.1+674f31e
ip-10-0-159-78.us-east-2.compute.internal Ready master 4h7m v1.22.1+674f31e
ip-10-0-179-69.us-east-2.compute.internal Ready worker 3h59m v1.22.1+674f31e
ip-10-0-184-212.us-east-2.compute.internal Ready master 4h6m v1.22.1+674f31e
ip-10-0-196-149.us-east-2.compute.internal Ready master 4h7m v1.22.1+674f31e
ip-10-0-219-207.us-east-2.compute.internal Ready worker 4h v1.22.1+674f31e
$ oc debug node/ip-10-0-156-16.us-east-2.compute.internal
Starting pod/ip-10-0-156-16us-east-2computeinternal-debug ...
sh-4.4# cat /etc/crio/crio.conf.d/* | grep version_file_persist
version_file_persist = "/var/lib/crio/version"
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.10.3 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.