UserWorkLoad components failures could still lead CMO degradation/unavailability

according to above epic, UserWorkLoad monitoring pods having any problem should not degrade ClusterMonitoringOperator(CMO). However CMO could still show as DEGRADED when UserWorkload Prometheus Operator Deployment failed.

    4.15.0-0.nightly-2023-11-22-143644

    always

    1.enable UWM

    2.
% oc apply -f -<<EOF
apiVersion: v1
kind: ConfigMap
metadata:
  name: user-workload-monitoring-config
  namespace: openshift-user-workload-monitoring
data:
  config.yaml: |
    prometheusOperator:
      resources:
        requests:
          cpu: 2m
          memory: 20Mi
        limits:
          cpu: 10m
          memory: 1Mi
EOF

    3. Wait a few minutes     

     % oc get co/monitoring
NAME         VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
monitoring   4.15.0-0.nightly-2023-11-22-143644   False       True          True       13m     UpdatingUserWorkloadPrometheusOperator: reconciling UserWorkload Prometheus Operator Deployment failed: creating Deployment object failed: Deployment.apps "prometheus-operator" is invalid: spec.template.spec.containers[0].resources.requests: Invalid value: "20Mi": must be less than or equal to memory limit of 1Mi

    CMO should not degraded