Description of problem: My cluster didn't have one by default so here is an example you can use to verify: ```yaml apiVersion: machineconfiguration.openshift.io/v1 kind: ContainerRuntimeConfig metadata: name: set-log-and-pid spec: machineConfigPoolSelector: matchLabels: debug-crio: config-log-and-pid containerRuntimeConfig: pidsLimit: 2048 logLevel: debug ``` Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Thanks for provided example resource, I have added it to cluster, and the archive contains: config/containerruntimeconfigs/set-log-and-pid.json Also checked, if collision of written records is possible - if it is possible to create the same resource in different namespace, and it wasn't possible to me. verified on 4.7.0-0.nightly-2020-10-15-011122
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.7.0 security, bug fix, and enhancement 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-2020:5633