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
Created attachment 1661614 [details]
Created attachment 1661615 [details]
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
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.