Bug 1656901

Summary: Webadmin - select storage domain Disks tab window - Virtual size column can not be sorted
Product: [oVirt] ovirt-engine Reporter: Avihai <aefrat>
Component: Frontend.WebAdminAssignee: Ahmad Khiet <akhiet>
Status: CLOSED CURRENTRELEASE QA Contact: Avihai <aefrat>
Severity: medium Docs Contact:
Priority: low    
Version: 4.3.0CC: bugs, mtessun, ratamir, tnisan
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_rc2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:45:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Video of the issue none

Description Avihai 2018-12-06 15:59:07 UTC
Created attachment 1512162 [details]
Video of the issue

Description of problem:
UI -> select a storage domain -> Disks tab - Virtual size column is not sorted.
You can press(hand sign) it but nothing happens. 
See video capture.

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


How reproducible:


Steps to Reproduce:
1.UI -> select a storage domain -> Disks tab - Virtual size column is not sorted.


Actual results:
You can press(hand sign) it but nothing happens. 
See video capture.

Expected results:
Virtual size column should be sortable

Additional info:

Comment 1 Avihai 2018-12-06 16:03:23 UTC
Version-Release number of selected component (if applicable):
ovirt-engine 4.3.0-0.2.master.20181128141347.git38908dd.el7

How reproducible:
100%

Comment 2 Avihai 2019-01-27 15:45:16 UTC
Verified at ovirt-engine 4.3.0-0.8.master.20190122121624.git9a8a519.el7

Comment 3 Sandro Bonazzola 2019-02-13 07:45:03 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.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.