Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-33863

Reason for broken UWM configmaps should be traceable back to UWM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.15.z
    • Monitoring
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

      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.    

              rh-ee-amrini Ayoub Mrini
              cbusse.openshift Claudio Busse
              Junqi Zhao Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: