Bug 1856583

Summary: Alert Rules can't display correct according to order of 'Alerting State'
Product: OpenShift Container Platform Reporter: hongyan li <hongyli>
Component: MonitoringAssignee: Andrew Pickering <anpicker>
Status: CLOSED ERRATA QA Contact: hongyan li <hongyli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:14:10 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:
Description Flags
Alert Rules order by 'Alerting State' none

Description hongyan li 2020-07-14 02:17:22 UTC
Created attachment 1700927 [details]
Alert Rules order by 'Alerting State'

Description of problem:
Open console, go to Monitoring->Alerting, click tab Alert Rules
Order Alert Rules by 'Alerting State'

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

How reproducible:

Steps to Reproduce:

Actual results:
Alert Rule can't be ordered by state Firing and Silence state 

Expected results:
Alert Rule should be ordered by state Firing and Silence state 

Additional info:

Comment 3 hongyan li 2020-08-04 08:33:36 UTC
Test with payload 4.6.0-0.nightly-2020-08-03-200401
Alert Rules display correctly according to order of 'Alerting State'

Comment 5 errata-xmlrpc 2020-10-27 16:14:10 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.