Bug 1872986

Summary:	Replace `Not Firing` Alert State with -
Product:	OpenShift Container Platform	Reporter:	Vikram Raj <viraj>
Component:	Dev Console	Assignee:	Vikram Raj <viraj>
Status:	CLOSED ERRATA	QA Contact:	Mohammed Saud <msaud>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	aos-bugs, msaud, nmukherj
Target Milestone:	---
Target Release:	4.6.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:	2020-10-27 16:34:36 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 Vikram Raj 2020-08-27 05:15:55 UTC

Description of problem:

For inActive rules, we are showing Alert State as `Not Firing` which considered confusing because it looked like it represented an additional alert state.

Steps to Reproduce:

1. Navigate to Monitoring Alerts tab
2. In the Alert State column see the Not Firing for inactive rules.

Actual results:
Not Firing Alert State has been shown for inactive rules.

Expected results:
Alert State should be - for inActive Alert State.

Reproducibility (Always/Intermittent/Only Once):
always

Build Details:
4.6.0-0.ci-2020-08-20-163422

Additional info:
https://coreos.slack.com/archives/G015E9G7DJN/p1598001784003500

Comment 3 Mohammed Saud 2020-09-23 11:09:02 UTC

Verified on -
build: 4.6.0-0.nightly-2020-09-22-213802
cluster: https://console-openshift-console.apps.jakumar-22091122.devcluster.openshift.com/
user: kubeadmin

Comment 5 errata-xmlrpc 2020-10-27 16:34:36 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 (OpenShift Container Platform 4.6 GA Images), 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:4196