Bug 1341162

Summary: [SR-IOV] - Specific networks list in the edit VFs dialog(in the PF) is out of the dialog range in case of multiple networks in the DC
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.0.2CC: awels, bugs, danken, mburman, myakove, ylavi
Target Milestone: ovirt-4.1.0-betaKeywords: Regression
Target Release: 4.1.0.2Flags: rule-engine: ovirt-4.1+
rule-engine: blocker+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 14:41:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
screenshot_3_6 none

Description Michael Burman 2016-05-31 11:58:04 UTC
Created attachment 1163194 [details]
screenshot

Description of problem:
[SR-IOV] - Specific networks list in the edit VFs dialog(in the PF) is out of the dialog range in case of multiple networks in the DC. 

If we have multiple networks in the DC(more then 13) and we want to edit the VF's allowed networks, the list of the networks is out of the dialog window range and it's looks pretty bad. 
And there is one network that can't be chosen(can't check the checkbox), the network that is in the end of the dialog's range(in one line with the 'OK" button).   

Version-Release number of selected component (if applicable):
4.1.0-0.0.master.20160529171307.git359707b.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Add sr-iov capable host to rhev 4.0
2. Create 15 networks 
3. Open setup networks and edit one of the PFs(pencil), select 'Specific networks' and try to check the last network in the list.

Actual results:
List is out of the range, looks bad.
Can't check the last network in the list(the 15' one)

Expected results:
There should be scrolling for the networks list in case of multiple networks in the DC

Comment 1 Yaniv Lavi 2016-06-01 09:49:12 UTC
Does this happen in 3.6?

Comment 2 Michael Burman 2016-06-01 14:17:12 UTC
No, on 3.6 we have a scrolling

Comment 3 Michael Burman 2016-06-01 14:17:55 UTC
Created attachment 1163699 [details]
screenshot_3_6

Comment 4 Dan Kenigsberg 2016-06-02 10:37:40 UTC
Alexander, was it triggered by your recent UI changes?

Comment 5 Red Hat Bugzilla Rules Engine 2016-06-02 10:37:45 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 6 Alexander Wels 2016-06-02 12:35:38 UTC
Potentially,

I changed the way the scrolling works in the dialogs, so this might be an unintended side effect.

Comment 7 Dan Kenigsberg 2016-06-05 07:05:06 UTC
Yaniv, please note that this issue is seen on 4.1.0-0.0.master.20160529171307.git359707b.el7.centos not on 4.0 branch. Please set the target milestone accordingly.

Comment 8 Michael Burman 2016-07-27 11:06:35 UTC
(In reply to Dan Kenigsberg from comment #7)
> Yaniv, please note that this issue is seen on
> 4.1.0-0.0.master.20160529171307.git359707b.el7.centos not on 4.0 branch.
> Please set the target milestone accordingly.

This issue is seen on 4.0.2

Comment 9 Dan Kenigsberg 2016-07-27 12:03:38 UTC
mburman, your recent comment is not clear. Which is the precise earliest version where this reproduces?

Comment 10 Alexander Wels 2016-07-27 12:24:45 UTC
Dan the problem probably appeared with the release of 4.0 upstream. I changed the way scroll bars work and I guess some of the dialogs depended on the broken behavior I fixed. The solution is to simply wrap the outer container in a ScrollPanel and it will be fine.

Comment 11 Michael Burman 2016-07-27 12:43:54 UTC
(In reply to Dan Kenigsberg from comment #9)
> mburman, your recent comment is not clear. Which is the precise earliest
> version where this reproduces?

It is very clear) 
This bug is relevant for 4.0.2
It reproduced on all the 4.0.z versions.

Comment 12 Michael Burman 2016-12-26 07:42:07 UTC
Verified on - 4.1.0-0.3.beta2.el7