Bug 1767182

Summary:	conformance test Prometheus when installed on the cluster should report less than two alerts in firing or pending state should include alert names when it fails
Product:	OpenShift Container Platform	Reporter:	Chance Zibolski <chancez>
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, kakkoyun, lcosic, mloibl, pkrupa, spasquie, surbania
Target Milestone:	---
Target Release:	4.2.z
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-12-03 22:43:11 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:	1766638
Bug Blocks:

Description Chance Zibolski 2019-10-30 21:08:43 UTC

Description of problem: Conformance has a test "[Feature:Prometheus][Conformance] Prometheus when installed on the cluster should have a Watchdog alert in firing state" which when it fails, does not indicate the alerts firing. It should be updated to include the alerts. Given this failure cannot be triaged without knowing what alert fails, this seems critical, especially with multiple related bugs on this failure being duplicates in bugzilla. 


Version-Release number of selected component (if applicable): 4.2.0 but it also shows in 4.3.0


How reproducible: 4 times in the last 24 hours, so relatively uncommon


Steps to Reproduce: 
1. Simply update conformance tests to produce an always failing alert to see that the alert name is not included in the logs.
2.
3.

Actual results: 

Failing tests:
[Feature:Prometheus][Conformance] Prometheus when installed on the cluster should report less than two alerts in firing or pending state [Suite:openshift/conformance/parallel/minimal]



Expected results:

Somewhere in the failing test output, indicate what alerts are firing.


Additional info:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-4.2/137#1:build-log.txt%3A12864

Comment 6 errata-xmlrpc 2019-12-03 22:43:11 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:3953