Description of problem: Updating clustercsidriver.spec.logLevel doesn't take effect, the CSI driver related pods don't restart and don't run as expected logLevel. From the config, seems loglevel is hardcoded as --v=5: https://github.com/openshift/vmware-vsphere-csi-driver-operator/blob/master/assets/controller.yaml https://github.com/openshift/vmware-vsphere-csi-driver-operator/blob/master/assets/node.yaml Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-04-09-222447 How reproducible: Always Steps to Reproduce: 1. Set Up an OCP4.8 cluster on vSphere 2. Enable TechPreviewNoUpgrade featureset 3. Edit the logLevel for csi.vsphere.vmware.com to TraceAll $ oc get clustercsidriver csi.vsphere.vmware.com -o json | jq .spec { "logLevel": "TraceAll", "managementState": "Managed", "observedConfig": null, "operatorLogLevel": "Debug", "unsupportedConfigOverrides": null } 4. Check the pods in openshift-cluster-csi-drivers 5. Check the loglevel Actual results: The Related pods should restart with "TraceAll" logLevel Expected results: The Related pods don't restart and the loglevel is not changed. $ oc -n openshift-cluster-csi-drivers logs vmware-vsphere-csi-driver-controller-8495967fc5-qzj97 -c csi-driver {"level":"info", ...
Thanks for the info @Fabio
Verified pass according to the test result above. The nightly 4.8.0-0.nightly-2021-04-19-** was used for verification.
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