Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1717632

Summary:	There should be cluster-monitoring alerts when an operator goes degraded or is unavailable
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Installer	Assignee:	Abhinav Dahiya <adahiya>
Installer sub component:	openshift-installer	QA Contact:	Junqi Zhao <juzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	bleanhar, juzhao, wking
Version:	4.2.0
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:
Clones:	1762920 (view as bug list)		Environment:
Last Closed:	2019-10-16 06:31:27 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:	1762920

Description Clayton Coleman 2019-06-05 20:34:26 UTC

There are no alerts currently for when a cluster operator goes degraded or unavailable.  We should have alerts for these.

We need to define how long is "bad" (5m?)

These should be back ported to 4.1.z so we can see them in telemetry and cluster administrators know what is happening.  These are important alerts.

We should identify whether the console dashboard should also show these if they're firing (since they're pretty critical)

Comment 1 W. Trevor King 2019-08-14 21:22:19 UTC

Brenton adjusted the Target Release to 4.2.0 on 2019-07-29.  I'm shifting Version to match, since this bug also affects the current 4.2 builds.  If we are planning on backporting fixes for 4.1.z, we should clone a separate bug for that.

Comment 2 W. Trevor King 2019-08-15 18:46:33 UTC

There's a bit of overlap between this effort and bug 1717617 (metrics for ClusterOperator conditions) and bug 1741645 (metrics for ClusterVersion conditions).  Those should be sufficient to feed Telemetry, although this bug's alerts feeding Telemetry too shouldn't hurt, and it also helps get the messages in front of the cluster's local admin who may be more likely to be monitoring their alerts than they are to be monitoring the metrics we're setting up to feed Telemetry.

Comment 6 errata-xmlrpc 2019-10-16 06:31:27 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-2019:2922