Bug 1068847 - [RFE] support flash lights to identify which nics belong to bond failed after setup bond with vlanid
Summary: [RFE] support flash lights to identify which nics belong to bond failed after...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Joey Boggs
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On: 1007311
Blocks: 1008280 1068848
TreeView+ depends on / blocked
 
Reported: 2014-02-22 08:52 UTC by haiyang,dong
Modified: 2016-02-10 19:39 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1007311
: 1068848 (view as bug list)
Environment:
Last Closed: 2014-10-17 12:20:04 UTC
oVirt Team: Node
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 24878 0 None None None Never

Description haiyang,dong 2014-02-22 08:52:07 UTC
+++ This bug was initially created as a clone of Bug #1007311 +++

Description of problem:
For after selecting "eth0" and "eth1" to set up bond0, then "bond0" will show in Available System NICs list of
Network page, then enter into "bond0" details page and clicking "Flash Lights to Identify" button to identify which nics belong to "bond0". 
this button support flash lights to identify which nics belong to bond.

But after setup bond0 with vlanid to configure network,then licking "Flash Lights to Identify" button to identify which nics belong to "bond0".
this button didn't work well.



Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.999.20140220121425git7628717.1242.el6.iso

How reproducible:
100% 
 
Steps to Reproduce:

Actual result:


Expect result:


Additional info:

--

Comment 1 Itamar Heim 2014-06-29 10:00:56 UTC
hadong - can you please clarify on reason for clone - both source and cloned bugs are on the ovirt prodcut?
(source has been closed, so this is probably done already, moving to ON_QA for caution)

Comment 2 haiyang,dong 2014-07-28 04:17:13 UTC
This bug has been fixed in the follow version:
ovirt-node-iso-3.5.0.ovirt35.20140707.el6.iso
ovirt-node-3.1.0-0.0.master.20140707.git2f40d75.el6.noarch

so change the status into "verified".

Comment 3 Sandro Bonazzola 2014-10-17 12:20:04 UTC
oVirt 3.5 has been released and should include the fix for this issue.


Note You need to log in before you can comment on or make changes to this bug.