Description of problem: The techPreviewUserWorkload field in CMO's configmap still allow users to configure user-workload-monitoring despite being deprecated since 4.6 and scheduled for removal in 4.8. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
reproduced with 4.8.0-0.nightly-2021-04-20-135853, no resources created under openshift-user-workload-monitoring and could see the warning info in CMO pod ********************* apiVersion: v1 kind: ConfigMap metadata: name: cluster-monitoring-config namespace: openshift-monitoring data: config.yaml: | techPreviewUserWorkload: enabled: true ********************* # oc -n openshift-user-workload-monitoring get all No resources found in openshift-user-workload-monitoring namespace. # oc -n openshift-monitoring logs $(oc -n openshift-monitoring get po | grep cluster-monitoring-operator | awk '{print $1}') -c cluster-monitoring-operator | grep techPreviewUserWorkload W0421 02:01:09.013026 1 operator.go:605] User Workload Monitoring enabled via the deprecated 'techPreviewUserWorkload' setting in "openshift-monitoring/cluster-monitoring-config" configmap. Use the 'enableUserWorkload' setting instead.
checked with 4.8.0-0.nightly-2021-04-20-195442 # oc -n openshift-user-workload-monitoring get all No resources found in openshift-user-workload-monitoring namespace. # oc -n openshift-monitoring logs $(oc -n openshift-monitoring get po | grep cluster-monitoring-operator | awk '{print $1}') -c cluster-monitoring-operator | grep techPreviewUserWorkload
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