Description of problem: [UI] - Add sorting for Cluster's columns. The Cluster's columns are missing the sorting option as we have for all columns in the system. The only sorting option which is available for Cluster column is 'Description' and 'Name'. We should add sorting for 'Cpu type', 'Data Center', 'Compatibility version', 'Host count' and 'VM count' Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170815155420.gitaed789a.el7.centos How reproducible: 100% Steps to Reproduce: 1. Have several clusters with different comparability versions 2. Go to 'Clusters' and try to sort clusters by comparability version Actual results: Missing sorting for most columns under Clusters It's not new thing as on older versions it behaved the same.
The reason is that the search does not support sorting by this columns, so it can not be exposed to the UI. Changing to an RFE.
Notes: I addressed the sorting for the following fields in the UI Cluster View: 1. CPU Type 2. Data Center 3. Compatibility Version These fields are included in the sql cluster view. Support for sorting the Host Count and VM Count will be more complex because they are fetched separately and are not included in the sql cluster view. To add them to the sql cluster view may have a performance impact because when the UI is connected, the sql cluster view is called to refresh the the cluster data and these are fields that are calculated by counting the number of vds_static and vm_static entries correlating to each cluster. Another option is to create another sql cluster view just for the sorting and make sure that for sorting only this is called, but this will require more infrastructure changes. The question is if it is worth the cost and if so, we may consider creating a separate RFE for this.
Let's do Host count and VM count in a separate RFE then.
Moving back to post since no target milestone has been set for this bug and it's not clear if it needs backport or not. Please target this bug.
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
Verified on - rhvm-4.4.0-0.29.master.el8ev.noarch
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.