Red Hat Bugzilla – Bug 1249900
[Setup Networks] - Improve the drag and drop Interfaces in SN dialog window when trying to create bond/s
Last modified: 2016-02-10 14:22:45 EST
Description of problem:
[Setup Networks] - Improve the drag and drop Interfaces in SN dialog window when trying to create bond/s.
When trying to create bond/s via Setup Networks in UI by dragging NICs on top of each other, it's not working smooth all the time, you need to be very accurate.
- For example, if trying to drag higher NIC to one below him, usually i will fail with the drag and drop and bond will not be created, i will need to find the exact point/spot and few more attempts in order to create this bond with success.
- When dragging lower NIC to one above him, usually i will succeed with the drag and drop on the first try and bond will be created with success.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Setup Networks dialog and try to create bond from 2 slaves by dragging and dropping higher NIC to one below him
Usually will fail with drag and drop on the first and second attempt
Drag and drop Interfaces on top of each other via Setup Networks should be more smooth and should succeed on first try.
I think the tooltip of the top nic covers the bottom nic, and it is what causes the issue.
(In reply to Alona Kaplan from comment #1)
> I think the tooltip of the top nic covers the bottom nic, and it is what
> causes the issue.
if that's the case, then this one is probably highly related to bug 1249895.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
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.
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 interface to anywhere on the target row (even directly an assigned logical network element) that is not covered by the tooltip and you'll be able to drop it there, initiating the dialog to create a new bond or update an existing bond.
Is there a specific browser or browser version that is more problematic?
Bug 1272857 is almost the same at this bug. This bug deals specifically with bonding interfaces (left column of Setup Host Networks). BZ 1272857 deals specifically with reassigning the logical networks (right column of Setup Host Networks).
Scott: BZ is flagged/targeted for ovirt 3.6, however I don't see that the patch has been backported to the ovirt-engine-3.6 branch - let's backport the patch to the following branches:
- ovirt-engine-3.6.1 , if exists (I updated the Target Milestone from ovirt-3.6.3 to ovirt-3.6.1).
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.
I'm testing this bug and it's much better now on 3.6.1-0.2.el6, the bonds creation is much smoother, but, on 60-80% of the time i'm failing to create bond when dragging higher NIC to one/s below him, because the NIC's tooltip preventing me from.
I believe this should be improved more, Scott, is this possible? can we improve this?
Please add a target release to this report, maybe we testing the wrong build and the fix is not in.
If the target release is 3.6.1, this bug should be failedQA.
(In reply to Michael Burman from comment #10)
> Please add a target release to this report, maybe we testing the wrong build
> and the fix is not in.
> If the target release is 3.6.1, this bug should be failedQA.
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', however *please do NOT move this BZ to failedQA*.
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-22.214.171.124.
Please set target release to 126.96.36.199 accordingly unless additional patches are needed.
(In reply to Sandro Bonazzola from comment #13)
> This bug is referenced in git log for ovirt-engine-188.8.131.52.
> Please set target release to 184.108.40.206 accordingly unless additional patches
> are needed.
Michael, my apologies - based on the above, TR for this BZ should be 220.127.116.11 and not 3.6.1 as I mentioned in my previous comment.
Same goes for Bug 1272857.
Verified on - 18.104.22.168-0.1.el6
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.