Created attachment 923776 [details]
The list should stretch to all page
Description of problem:
[RHEVM GUI] in 'Add Users and Groups' dialog The list should stretch to all page.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.4.0-0.21.el6ev
oVirt Engine Version: 3.5.0-0.0.master.20140715172116.git4687dc1.el6
Steps to Reproduce:
Go to Users tab and click on Add.
The 'Add Users and Groups' Dialog opened with unused space in the bottom of the list.
To use all the dialog space to present the users and groups list.
see attached snapshot
this dialog is being used also for adding permissions, I am guessing that the leftover space at the bottom is the one used to display the Role drop-down in case of permissions granting.
we have a similar issue in the confirmation dialog (see bug 966427), not sure if there is a quick and easy solution for this issue.
[moving to 'NEW', even though there is a patch, since the patch doesn't seem to solve the problem properly]
we will look into that when migrating dialogs to PatternFly.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
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 ?.
Created attachment 1361085 [details]
looks good in 4.2
Where is the relevant tracker for this bug? I see one which is abandoned?
On which engine version was this fixed?
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[No relevant external trackers attached]
For more info please contact: email@example.com
It was fixed in the 4.2 redesign, but I have no idea which specific patch.
Verified in RHEVM 18.104.22.168-0.1.el7
Verified by following the reproducer.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.