Bug 1841105

Summary: Alert TemplateServiceBrokerEnabled doesn't have message
Product: OpenShift Container Platform Reporter: Fan Jia <jfan>
Component: Service BrokerAssignee: Jesus M. Rodriguez <jesusr>
Status: CLOSED ERRATA QA Contact: Fan Jia <jfan>
Severity: medium Docs Contact:
Priority: low    
Version: 4.5CC: aos-bugs
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1841099 Environment:
Last Closed: 2020-07-13 17:42:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1841099    

Description Fan Jia 2020-05-28 11:29:28 UTC
Description of problem:
The alert TemplateServiceBrokerEnabled doesn't have message to describe the content about the alert.

Version-Release number of selected component (if applicable):
cv: 4.4.5
template broker version:openshifttemplateservicebrokeroperator.4.4.0-202005252114

How reproducible:
always

Steps to Reproduce:
1.install templateservicebrokeroperator in the cluster
2. Check the alert about "TemplateServiceBrokerEnabled" in console "Monitoring-Alerting"

Actual results:
1.The alert "TemplateServiceBrokerEnabled" is firing, but no message to describe this alert.

Expected results:
1.The alert "TemplateServiceBrokerEnabled" should have "message" field to describe itself.
  spec:
    groups:
    - name: template-service-broker-enabled
      rules:
      - alert: TemplateServiceBrokerEnabled
        annotations:
          summary: Indicates whether the Template Service Broker is enabled
          message : Indicates whether the Template Service Broker is enabled

Additional info:

Comment 1 Fan Jia 2020-05-28 11:32:39 UTC
Verified this bug since the template-service-broker is removed from ocp4.5

Comment 3 errata-xmlrpc 2020-07-13 17:42:23 UTC
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:2409