Bug 1812258

Summary: Operand list status sort only checks status.phase, which is different from what we show in the column
Product: OpenShift Container Platform Reporter: bpeterse
Component: Management ConsoleAssignee: Joe Caiani <jcaiani>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jcaiani, jokerman, spadgett, yapei
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1812076 Environment:
Last Closed: 2020-05-04 11:45:45 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: 1812076    
Bug Blocks:    
Attachments:
Description Flags
Sort on Status
none
Sort on Status - phase none

Description bpeterse 2020-03-10 20:35:28 UTC 
+++ This bug was initially created as a clone of Bug #1812076 +++

Version 4.4

https://github.com/openshift/console/pull/3121 added the capability to show different status values from the operand. It didn't update the table sort, however, so the result of sorting on the status column will not match the display value. We either need to disable sort or add a `sortFunc` that has the same logic.
Comment 3 Yadan Pei 2020-03-20 08:07:43 UTC 
Created attachment 1671711 [details]
Sort on Status
Comment 4 Yadan Pei 2020-03-20 08:08:59 UTC 
Created attachment 1671712 [details]
Sort on Status - phase
Comment 5 Yadan Pei 2020-03-20 08:14:11 UTC 
1. Install some operators like Kiali Operator, AMQ Streams Operator and create custom resource
2. When Status column is showing status as text Condition: xxx  or Phase: xxx, sort by Status column, the sorting works


Verified on 4.4.0-0.nightly-2020-03-19-205629
Comment 7 errata-xmlrpc 2020-05-04 11:45:45 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:0581