Bug 1732939

Summary: >30 clusters have firing ClusterMonitoringOperatorErrors alerts or report degraded
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: MonitoringAssignee: Frederic Branczyk <fbranczy>
Status: CLOSED CURRENTRELEASE QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: alegrand, anpicker, erooth, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-04 11:18:47 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:

Description Clayton Coleman 2019-07-24 19:00:07 UTC 
It's not clear what the breakdown of issues is.  A few clusters have problems with other operators (like kcm).  Some may be UPI and be incomplete.  Needs to be broken down into individual bugs or the key error found (I would expect degraded should not be happening except possibly for incomplete UPI clusters which we should have a metric on soon).

I also notice the operator sets no Reason, so if we need to be reporting reason on the operator to break into rough classes of error we should get that fixed in 4.2.
Comment 6 Red Hat Bugzilla 2023-09-14 05:32:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days