Bug 1781798

Summary: alert name prefixes (CCO) are too generic
Product: OpenShift Container Platform Reporter: Joel Diaz <jdiaz>
Component: Cloud Credential OperatorAssignee: Joel Diaz <jdiaz>
Status: CLOSED ERRATA QA Contact: Xiaoli Tian <xtian>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1781792 Environment:
Last Closed: 2020-01-23 11:18:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1781792    
Bug Blocks:    

Description Joel Diaz 2019-12-10 15:39:14 UTC
+++ This bug was initially created as a clone of Bug #1781792 +++

Description of problem:
CCO is far too generic to be an alert name and confused an
admin when looking at clusters.

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

How reproducible:

Steps to Reproduce:
1. Look at the 'CCO' abbreviations for the defined alerts. 

Actual results:

Expected results:
Instead of 'CCO', spell out 'CloudCredentialOperator' for the alert names.

Additional info:

Comment 2 Oleg Nesterov 2019-12-12 09:20:53 UTC
Verified on 4.3.0-0.nightly-2019-12-12-021332

Comment 5 errata-xmlrpc 2020-01-23 11:18:20 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.