+++ This bug was initially created as a clone of Bug #1777753 +++ Description of problem: No message defined for ServiceCatalogControllerManagerEnabled and ServiceCatalogAPIServerEnabled alert, we can't see detail info for these alerts when viewing them on console Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-27-041100 How reproducible: Always Steps to Reproduce: 1. Check ServiceCatalogControllerManagerEnabled and ServiceCatalogAPIServerEnabled alert rules alert: ServiceCatalogControllerManagerEnabled expr: service_catalog_controller_manager_enabled > 0 labels: severity: warning annotations: summary: Indicates whether Service Catalog Controller Manager is enabled alert: ServiceCatalogAPIServerEnabled expr: service_catalog_apiserver_enabled > 0 labels: severity: warning annotations: summary: Indicates whether Service Catalog API Server is enabled 2. Check other alert rules alert: AlertmanagerFailedReload expr: alertmanager_config_last_reload_successful{job="alertmanager-main",namespace="openshift-monitoring"} == 0 for: 10m labels: severity: warning annotations: message: Reloading Alertmanager's configuration has failed for {{ $labels.namespace }}/{{ $labels.pod}}. Actual results: Only have summary, no messages. If alert has no messages, it will not show useful message/info on web console Monitoring -> Alerts or Home -> Dashboards page Expected results: ServiceCatalogControllerManagerEnabled and ServiceCatalogAPIServerEnabled alert should have message defined Additional info:
cv:4.4.0-0.nightly-2019-12-15-184910 result: 1. enable the ServiceCatalogAPIServer and the alert console has the firing and the message ServiceCatalogAPIServerEnabled Indicates whether Service Catalog API Server is enabled 2.enable the ServiceCatalogControllerManager and the alert console has the firing and the message ServiceCatalogControllerManagerEnabled Indicates whether Service Catalog Controller Manager is enabled
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581