Bug 2069193

Summary: while checking cluster operator from web console. clicking on the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is done based on the name of the operator instead.
Product: OpenShift Container Platform Reporter: bshaw <bshaw>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: aos-bugs, rhamilto, sigbjorn.tvedt
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Other   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-28 15:37:19 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:
Attachments:
Description Flags
while checking cluster operator from web console. clicking on the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is do none

Description bshaw 2022-03-28 12:58:36 UTC
Created attachment 1868708 [details]
while checking cluster operator from web console.  clicking on  the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is do

Description of problem:

while checking cluster operator from web console.  clicking on  the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is done based on the name of the operator instead. Please refer attached screen shot
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Robb Hamilton 2022-03-28 15:37:19 UTC

*** This bug has been marked as a duplicate of bug 2066298 ***