Created attachment 876225 [details] attached Screenshot for createBondDialog Description of problem: Clean install rhevh-6.5-20140317.0.iso, then enter into network page, check that there were three nics "eth0,eth1,eth2", then configure "eth0" to be up, and then enter into createBondDialog and check that nictable of createBondDialog will list all nics.(seen createBondDialog.png) Better to filter out nics that was managed by rhevm or configured for nictable of createBondDialog Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34rc2.el6.iso How reproducible: 100% Steps to Reproduce: Actual results: Expected results:
The combination of not showing NICs which are configured (https://bugzilla.redhat.com/show_bug.cgi?id=1078087) and not allowing users to create new bonds when managed by RHEV-M (https://bugzilla.redhat.com/show_bug.cgi?id=1083138) will resolve. I'd like to close this as a duplicate.
(In reply to Ryan Barry from comment #1) > The combination of not showing NICs which are configured > (https://bugzilla.redhat.com/show_bug.cgi?id=1078087) and not allowing users > to create new bonds when managed by RHEV-M > (https://bugzilla.redhat.com/show_bug.cgi?id=1083138) will resolve. > > I'd like to close this as a duplicate. I report this bug in ovirt-node upstream component, since there two branches for upstream and downstream for ovirt-node, i think it's better to keep this bug as open to track this issue in upstream
Since downstream mirrors upstream, the relevant patches for those bugs are already present: http://gerrit.ovirt.org/#/c/26626/ http://gerrit.ovirt.org/#/c/26339/ Users will not be able to see configured NICs in the createBond dialog or use the createBond dialog when registered to ovirt-engine upstream either. It'll still be an unresolvable bug when those patches merge, and the issue will not exist upstream.
Verified in rhev-hypervisor6-6.6-20141007.0