+++ This bug was initially created as a clone of Bug #1819953 +++ 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:
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