-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.15.z
-
None
-
Moderate
-
No
-
False
-
Description of problem:
Creating a faulty configmap for UWM results in cluster_operator_up=0 with the reason InvalidConfiguration. With https://issues.redhat.com/browse/MON-3421 we're expecting the reason to match UserWorkload.*
Version-Release number of selected component (if applicable):
4.15.z
How reproducible:
100%
Steps to Reproduce:
apply the following CM to a cluster with UWM enabled: apiVersion: v1 kind: ConfigMap metadata: name: user-workload-monitoring-config namespace: openshift-user-workload-monitoring data: config.yaml: | hah helo! :)
Actual results:
cluster_operator_up=0 with reason InvalidConfiguration
Expected results:
cluster_operator_up=0 with reason matching pattern UserWorkload.*
Additional info:
https://issues.redhat.com/browse/MON-3421 streamlined reasons to allow separation between UWM and cluster monitoring. The above is a leftover that should be updated to match the same pattern.
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update