Hide Forgot
Created attachment 1158178 [details] Screenshot of the unknown driver for bond devices. Description of problem: Just a cosmetic issue as all the underlying settings are fine. When a bonding device is configured, the driver is showing as unknown in the Network tab, after entering in the device configuration. See screenshot attached for clarification. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Hypervisor release 7.2 (20160413.0.el7ev) How reproducible: 100% Steps to Reproduce: 1. Setup Bond using RHEV-H UI 2. Check the status as shown in attachment Actual results: NIC details: bond0 Driver: unknown Link Status: Connected # ethtool -i bond0 | grep driver driver: bonding Expected results: NIC details: bond0 Driver: bonding Link Status: Connected Additional info: If it's a VLAN (bond0.VID) should be show the 8021q driver?
Thanks for the report. It looks liek this issue will be fixed in RHEV 4.0, where we are moving to Cockpit for the initial network administration.
However, this will not be fixed in the current text UI.
Hi Fabian, How can i test it? i don't see any 'Driver' field in the cockpit UI..
Created attachment 1170870 [details] Screenshot showing the driver location in Cockpit Yes - There is no explicit driver field, but the driver is shown alongside the NIC name - see the attached screenshot for the exact location.
Thank you Fabian) i will test it.
Created attachment 1171410 [details] screen shot of a bond's driver
I'm not this is what i expected to see, i don't see the driver info for the bond NIC. Is the the 'Bond'? isn't should be 'bonding'? Attaching screen shot from cockpit-0.108-1.el7.x86_64 ^^
To me "Bond" or "bonding" is sufficient. The driver of the underlying bond slaves is not shown, because there can be a large number of underlying slaves with different drivers (which should not be done, because it can be unstable). To me it is sufficient that "Bond" is shown instead of "unknown".
Verified on - cockpit-0.108-1.el7.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1702.html