Bug 1243444

Summary: Inconsistent sorting in VMs tab in webadmin
Product: Red Hat Enterprise Virtualization Manager Reporter: Petr Matyáš <pmatyas>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.4CC: gklein, lsurette, mgoldboi, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ovirt-3.6.0-rc   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.6.0-4 alpha3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-20 01:28:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshots - sorting FQDN and description none

Description Petr Matyáš 2015-07-15 13:03:23 UTC
Created attachment 1052353 [details]
Screenshots - sorting FQDN and description

Description of problem:
When you sort VMs by host, items with value are always first.
If you use uptime, in ascending items without value are first and in descending last.
If you use FQDN or description, in ascending it's weird (see pictures), in descending items without value are last.

Version-Release number of selected component (if applicable):
3.5.4

How reproducible:
always

Steps to Reproduce:
1. have installed RHEVM with some VMs
2. try sorting by fields suggested in description
3.

Actual results:
inconsistent sorting

Expected results:
consistent sorting

Additional info:

Comment 1 Einav Cohen 2015-07-16 14:07:53 UTC
currently marking on 'infra', may change based on response to needinfo in bug 1127727.

Comment 2 Einav Cohen 2015-07-22 11:43:57 UTC
summary:

"""
When you sort VMs by host, items with value are always first.
"""

this behavior is by design per bug 962560. 

however, based on bug 1127727, comment #9, it seems like we want to disable this behavior and simply include nulls as part of the sort; 
so if sort is ascending, nulls should be first; if sort is descending - nulls should be last. 

this should be modified in the search mechanism.

Comment 3 Petr Matyáš 2015-07-22 11:46:46 UTC
Sorry, I didn't clarify, I've been told that the first case is desired one and is written there just for comparison.

Comment 4 Eli Mesika 2015-07-26 07:36:38 UTC
Moran 

Please approve change described by Einav in comment 2

Comment 5 Petr Matyáš 2015-07-28 11:24:54 UTC
Verified on ovirt-engine-3.6.0-0.0.master.20150727175355.git0d51373.el6.noarch