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

PrometheusOperatorRejectedResources alert fires on Hypershift clusters with user-defined monitoring

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • 4.16.0
    • 4.14
    • Monitoring
    • Moderate
    • No
    • MON Sprint 245
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

    Description

      Description of problem:

      After enabling user-defined monitoring on an HyperShift hosted cluster, PrometheusOperatorRejectedResources starts firing.

      Version-Release number of selected component (if applicable):

      4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1. Start an hypershift-hosted cluster with cluster-bot
      2. Enable user-defined monitoring
      3.
      

      Actual results:

      PrometheusOperatorRejectedResources alert becomes firing

      Expected results:

      No alert firing

      Additional info:

      Need to reach out to the HyperShift folks as the fix should probably be in their code base.

      Attachments

        1. prometheus-operator.log
          19 kB
          Simon Pasquier
        2. Screenshot from 2023-08-25 13-47-22.png
          111 kB
          Simon Pasquier

        Activity

          People

            mariofer@redhat.com Mario Fernandez Herrero
            spasquie@redhat.com Simon Pasquier
            Junqi Zhao Junqi Zhao
            Simon Pasquier
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: