Bug 1791200

Summary:	Lack of configured alertmanager routes should be surfaced as an alert
Product:	OpenShift Container Platform	Reporter:	Pawel Krupa <pkrupa>
Component:	Monitoring	Assignee:	Pawel Krupa <pkrupa>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	alegrand, anpicker, erooth, juzhao, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1791198
Clones:	1791211 (view as bug list)		Environment:
Last Closed:	2020-03-10 23:52:55 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:	1791198
Bug Blocks:	1791211

Description Pawel Krupa 2020-01-15 08:35:05 UTC

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

Description of problem:
Prometheus should fire an alert when there is no routes configured in alertmanager


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

How reproducible:
always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Based on https://coreos.slack.com/archives/C0VMT03S5/p1575909697091600 and https://github.com/openshift/cluster-monitoring-operator/pull/554#issuecomment-561922011

BZ made for backporting purposes

Comment 5 errata-xmlrpc 2020-03-10 23:52:55 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:0676