Bug 1762920

Summary:	There should be cluster-monitoring alerts when an operator goes degraded or is unavailable
Product:	OpenShift Container Platform	Reporter:	W. Trevor King <wking>
Component:	Cluster Version Operator	Assignee:	W. Trevor King <wking>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.1.z	CC:	adahiya, aos-bugs, bleanhar, ccoleman, jokerman, juzhao, wking
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1717632	Environment:
Last Closed:	2020-01-09 09:16: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:
Embargoed:
Bug Depends On:	1717632
Bug Blocks:

Description W. Trevor King 2019-10-17 19:41:06 UTC

+++ This bug was initially created as a clone of Bug #1717632 +++

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 Scott Dodson 2019-12-20 14:52:02 UTC

All associated PRs have merged, moving to MODIFIED.

Comment 5 errata-xmlrpc 2020-01-09 09:16: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.

https://access.redhat.com/errata/RHBA-2020:0010