Bug 830671 - [WEBADMIN] - Its impossible to configure all 7 types of bond from bond drop down list for the bridgeless network
Summary: [WEBADMIN] - Its impossible to configure all 7 types of bond from bond drop d...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks: 844947
TreeView+ depends on / blocked
 
Reported: 2012-06-11 07:54 UTC by GenadiC
Modified: 2016-02-10 19:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 844947 (view as bug list)
Environment:
Last Closed: 2013-03-03 21:39:04 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
png showing 4 bond modes instead of 7 (1.48 MB, image/png)
2012-06-11 07:54 UTC, GenadiC 		no flags Details
View All

Description GenadiC 2012-06-11 07:54:18 UTC 
Created attachment 590837 [details]
png showing 4 bond modes instead of 7

Description of problem:
It should be possible to choose all 7 bond modes from the bond drop down list for bridgess network and not only 4 bond modes (as it today for the bridged network)

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.Perform bond of 2 NICs for specific host
2. Open drop down menu for the bonding mode for the bridgless network
3.
  
Actual results:

Only 4 bond modes are available

Expected results:

All 7 bond modes should be available for the bridgeless network

Additional info:
Comment 1 lpeer 2012-06-14 11:55:22 UTC 
lowering priority and sevirity as the user can use the custom mode and configure any bond mode he wants.
Comment 2 Shahar Havivi 2012-08-07 11:01:29 UTC 
posted at: http://gerrit.ovirt.org/#/c/6974/
Comment 4 Itamar Heim 2013-03-03 21:39:04 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Note You need to log in before you can comment on or make changes to this bug.