Description of problem:
when trying to change order of apiVersion on CustomResourceDefinitions list page , the sorting doesn't work as expected
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. admin user goes to CustomResourceDefinitions list page /k8s/cluster/customresourcedefinitions
2. Click the arrow to change data order of 'Latest version' column
2. the order result is not correct
2. the results should be ordered correctly
It looks like `sortFunc` is broken everywhere and not just on the CRD apiVersion col. I believe https://github.com/openshift/console/commit/3f127123faf52d7ef4effee4a98b093c63ee08f6#diff-88910eaad88244e5a1a05c0af91ff4e2691f9b916abf4a77575db876414b1b15 is the last good commit. Raising the severity as a result of this affecting all tables using `sortFunc`.
This bug appears to have been introduced with https://github.com/openshift/console/pull/8756
The original issue that sorting by 'Latest version' doesn't work on CustomResourceDefinitions list page has been fixed.
Also checked some other sorting on resources list page, such as Pods list, Projects list, Nodes list page, all sorting is working as expected now
Verified on 4.9.0-0.nightly-2021-07-29-103526
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.