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

Unable to see the Alerts in his developer webUI

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.17.z
    • 4.17.z
    • Observability UI
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 2
    • None
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      * Previously, the *Alerts* page on the Developer perspective of the web console stopped querying the Prometheus tenancy path. This issue caused an `Error loading silences from alert manager` banner to show on the page. With this release, the page now queries the Prometheus tenancy path and the page retrieves silent alert data from the Developer perspective data store so that the banner no longer shows on the page. (link:https://issues.redhat.com/browse/OCPBUGS-54211[*OCPBUGS-54211*])
      Show
      * Previously, the *Alerts* page on the Developer perspective of the web console stopped querying the Prometheus tenancy path. This issue caused an `Error loading silences from alert manager` banner to show on the page. With this release, the page now queries the Prometheus tenancy path and the page retrieves silent alert data from the Developer perspective data store so that the banner no longer shows on the page. (link: https://issues.redhat.com/browse/OCPBUGS-54211 [* OCPBUGS-54211 *])
    • None
    • None
    • None
    • None

      Description of problem:

      Unable to see Alerts in the Developer UI after upgrading the cluster from 4.16 to 4.17.

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

        4.17.15

      How reproducible:

      Add the ClusterRole monitoring-rules-view and monitoring-edit to the edit cluster Role via the aggregate-to-edit Annotation[ https://access.redhat.com/solutions/4213841 ].

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

      --> The same is working fine with clusters of 4.16 but as soon as we upgrade the cluster to 4.17, alerts can't be seen.
--> The URL that the users cant see anymore is: https://<CLUSTER>/dev-monitoring/ns/<PROJECT>/alerts
--> In the developer console you can see a 403-error for the endpoints /api/alertmanager/api/v2/silences/rules and /api/alertmanager/api/v2/silences.

              rh-ee-pyurkovi Peter Yurkovich
              rhn-support-shupadhy Shivam Upadhyay
              None
              None
              Junqi Zhao Junqi Zhao
              None
              Votes:
              7 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: