Bug 1686717

Summary: UI Dialog for moving disks between Storagedomains is less useful
Product: [oVirt] ovirt-engine Reporter: Steffen Froemer <sfroemer>
Component: Frontend.WebAdminAssignee: Ahmad Khiet <akhiet>
Status: CLOSED CURRENTRELEASE QA Contact: Daniel <dmaaravi>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, tnisan
Target Milestone: ovirt-4.3.6Flags: pm-rhel: ovirt-4.3+
Target Release: 4.3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-26 19:43:07 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
Screenshot of dialog
none
move_disk_dialog_fix none

Description Steffen Froemer 2019-03-08 06:14:34 UTC
Created attachment 1542050 [details]
Screenshot of dialog

Description of problem:
The UI dialog for moving disks between storage domains is to small. If one try to move several disks, it might happen, the last ones is not possible to select the target storage domain, as it's covered by scrollbars or unable to reach.
Also the width of drop-down menu is too small, that content is not fully visible.

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

How reproducible:
100%

Steps to Reproduce:
1. Open Menu Storage -> Disks
2. select several disks (Strg + left Mousebutton)
3. Open move Dialog via Contextmenu (Right mousebutton)

Actual results:
too small UI

Expected results:
A UI dialog with proper sizing

Additional info:

Comment 1 Daniel 2019-08-20 12:03:44 UTC
Created attachment 1606061 [details]
move_disk_dialog_fix

Verified on version: ovirt-engine-4.3.6.2-0.1.el7.noarch
Attached print-screen.

Comment 2 Sandro Bonazzola 2019-09-26 19:43:07 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

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