Description of problem:. the logLevel field in containerruntimeconfig can't be set to "trace". According to 4.6 doc, the logLevel field can be set to trace: https://docs.openshift.com/container-platform/4.6/post_installation_configuration/machine-configuration-tasks.html#create-a-containerruntimeconfig_post-install-machine-configuration-tasks Version-Release number of selected component (if applicable): 4.7.0-0.nightly-2021-02-17-224627 How reproducible: always Steps to Reproduce: 1.oc label mcp worker custom-loglevel=trace 2.oc create -f containerRuntimeConfig_log_level.yaml apiVersion: machineconfiguration.openshift.io/v1 kind: ContainerRuntimeConfig metadata: name: set-loglevel spec: machineConfigPoolSelector: matchLabels: custom-loglevel: trace containerRuntimeConfig: logLevel: trace 3.oc get ctrcfg set-loglevel -o yaml Actual results: 3.show following error: - lastTransitionTime: "2021-02-19T08:56:28Z" message: 'Error: invalid LogLevel "trace", must be one of error, fatal, panic, warn, info, or debug' status: "False" type: Failure Expected results: 3.the ctrcfg can accept "trace" as loglevel Additional info:
verified on version : 4.8.0-0.nightly-2021-03-01-143026
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