Red Hat Bugzilla – Bug 1272857
[Setup Networks] UI - Network's tooltip preventing from dragging the network and attaching it to the NIC/s below(if it's already attached to a NIC)
Last modified: 2016-02-10 14:22:45 EST
Description of problem:
[Setup Networks] UI - Network's tooltip preventing from dragging the network and attaching it to the NIC below.
It is not possible to drag and attach network from one NIC to the one below it in the Setup Networks dialog, because the network tooltip is shown once touching/hoovering the network and it prevents from attaching the network on the NIC/s below.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attach network to first or second NIC on host via Setup Networks
2. Try to drag and attach this network to the NIC/s below in the Setup Networks dialog
It's not possible to drag and attach the networks to the NIC/s below(if it's already attached to upper NIC), because the network's tooltip is shown once touching/hoovering the network.
Should be able to drag and attach network to all NICs on server. Network's tooltip shouldn't prevent me from doing so.
related to and/or duplicate of bug 1249900 and/or bug 1249895.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Scott and I reproduced on master.
Scott may have a workaround while he works on a fix. Scott -- can you update?
On the Setup Host Networks dialog, the tooltip on the draggable "Interface" and "Assigned Logical Networks" elements do indeed block the drop targets of the interfaces below the source element. The tooltip should disappear when the dragging starts for the best user experience.
Until a fix is finalized, there is a work around. The drop target is actually the entire row containing the interface and assigned logical network. Drag the logical network to anywhere on the target row (even directly on the nic/bond element) that is not covered by the tooltip and you'll be able to drop it there, reassigning the logical network to a new nic/bond.
Is there a specific browser or browser version that is more problematic?
Bug 1249900 is almost the same at this bug. This bug deals specifically with reassigning the logical networks (right column of Setup Host Networks). BZ 1249900 deals specifically with bonding interfaces (left column of Setup Host Networks).
Scott, please see bug 1249900, comment #6. thanks.
gerrit patch 48873 backports to ovirt-engine-3.6
gerrit patch 48874 backports to ovirt-engine-3.6.1
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Please add a target release to this report, so we can be sure we testing the right qa build.
As it looks on 3.6.1-0.2.el6, this bug is still relevant and in most of 60-95% of the time, the network's tooltip is preventing from drag and attach the network to lower NIC/s (if it's already attached to NIC) .
(In reply to Michael Burman from comment #9)
> Hi Scott,
> Please add a target release to this report, so we can be sure we testing the
> right qa build.
> As it looks on 3.6.1-0.2.el6, this bug is still relevant and in most of
> 60-95% of the time, the network's tooltip is preventing from drag and attach
> the network to lower NIC/s (if it's already attached to NIC) .
It seems that the fix hasn't made it into the latest 3.6.1 build (3.6.0-22), however it should make it into tomorrow's build, which is also a 3.6.1 build AFAIK.
So I am setting the Target Release of this BZ as '3.6.1' (please do NOT move this BZ to failedQA or anything like that).
This BZ should move to ON_QA once tomorrow's build is released, then verified.
Will be tested (and verified) once we have the new build.
Thanks for your response.
This bug is referenced in git log for ovirt-engine-220.127.116.11.
Please set target release to 18.104.22.168 accordingly unless additional patches are needed.
Verified on 22.214.171.124-0.1.el6
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.