Bug 1798182

Summary: Operand tab order reversed on Installed Operators page
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jokerman, xiaocwan
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.4.0-0.ci-2020-02-04-101704 Cluster ID: 30e82a96-378b-4183-a31f-4e87ca9b8663 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Last Closed: 2020-05-04 11:33:07 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
correct-order-on-list-detail-column
none
correct-order-on-detail-page-header-scroll-line none

Description Samuel Padgett 2020-02-04 18:24:47 UTC
The order of operand resource kinds is reversed from how it is declared in the ClusterServiceVersion YAML `spec.customresourcedefinitions.owned`

Regression from https://github.com/openshift/console/pull/3877

Comment 2 XiaochuanWang 2020-02-07 07:09:04 UTC
Created attachment 1661614 [details]
correct-order-on-list-detail-column

Comment 3 XiaochuanWang 2020-02-07 07:09:55 UTC
Created attachment 1661615 [details]
correct-order-on-detail-page-header-scroll-line

Comment 4 XiaochuanWang 2020-02-07 07:15:42 UTC
Now the order is correctly same as ClusterServiceVersion yaml order of `spec.customresourcedefinitions.owned`

Checked two places:
1) Installed Operators page for list column "Provided APIs" 
2) Operator "OpenShift Container Storage" detail page for header list scroll bar.

Attached screenshots for both two place.
Verified on 4.4.0-0.nightly-2020-02-06-230833

Comment 7 errata-xmlrpc 2020-05-04 11:33:07 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