Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-10082

Failed to find exact match for monitoring.rhobs/v1.prometheus

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • CloudOps 2024 Sprint 18
    • Moderate

      Some customers hit the following error when deploying STF with observabilityStrategy: use_community, the Prometheus Operator deployed, and no COO.

      2024-06-27T05:24:43.253007084Z TASK [Ensure no rhobs Prometheus is installed if not using it] ********************************
      2024-06-27T05:24:43.253007084Z fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to find exact match for monitoring.rhobs/v1.prometheus by [kind, name, singularName, shortNames]"}
      

      The workaround for these cases is to deploy COO anyways, deploy Prometheus community operator, deploy STF with use_community strategy and then disable COO.

      Related change: https://github.com/infrawatch/service-telemetry-operator/pull/421

              csibbitt-rh Chris Sibbitt
              rhn-engineering-vimartin Victoria Martinez de la Cruz
              rhos-dfg-cloudops
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: