Bug 830671

Summary: [WEBADMIN] - Its impossible to configure all 7 types of bond from bond drop down list for the bridgeless network
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: ovirt-engineAssignee: lpeer <lpeer>
Status: CLOSED WONTFIX QA Contact: GenadiC <gcheresh>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: abaron, acathrow, dyasny, iheim, lpeer, Rhev-m-bugs, shavivi, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 844947 (view as bug list) Environment:
Last Closed: 2013-03-03 21:39:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 844947    
Attachments:
Description Flags
png showing 4 bond modes instead of 7 none

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.