Bug 1819953

Summary: Custom OperatorSource or any CatalogSourceConfig should create a Promethues alert
Product: OpenShift Container Platform Reporter: Anik <anbhatta>
Component: OLMAssignee: Anik <anbhatta>
OLM sub component: OLM QA Contact: kuiwang
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: agreene, ecordell
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1823204 (view as bug list) Environment:
Last Closed: 2020-05-04 11:47:45 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: 1823204    
Bug Blocks:    

Description Anik 2020-04-01 22:05:58 UTC
Description of problem:
The presence of a CatalogSourceConfig or a custom (non-default) OperatorSource does not create a Prometheus alert.

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

How reproducible:
Always

Steps to Reproduce:
1. Launch OCP 4.4 cluster
2. 

oc apply -f csc.yaml

``` csc.yaml
apiVersion: "operators.coreos.com/v1"
kind: "CatalogSourceConfig"
metadata:
  name: "installed-redhat-operators"
  namespace: openshift-marketplace
spec:
  targetNamespace: openshift-marketplace
  source: redhat-operators
  packages: jaeger-product,kiali-ossm,elasticsearch-operator,servicemeshoperator
```
3. Check Monitoring -> Alerts tag in UI

Actual results:
No alerts related to presence of custom resources.

Expected results:
Alert indicating the presence of a custom resource.

Additional info:

Comment 5 errata-xmlrpc 2020-05-04 11:47:45 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:0581