Bug 844947 - [Documentation] - It's impossible to configure all 7 types of bond from bond drop down list for the bridgeless network
Summary: [Documentation] - It's impossible to configure all 7 types of bond from bond ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Tim Hildred
QA Contact: ecs-bugs
URL:
Whiteboard: network
Depends On: 830671
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-01 10:35 UTC by Simon Grinberg
Modified: 2016-02-10 19:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 830671
Environment:
Last Closed: 2012-12-04 17:25:55 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Simon Grinberg 2012-08-01 10:35:13 UTC
+++ This bug was initially created as a clone of Bug #830671 +++

This bug is cloned in order to document that using other bonding mode is available today only using custom. Please give example per all 3 types that are not in the menu. 

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)

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
  
Actual results:
Only 4 bond modes are available

Expected results:
All 7 bond modes should be available for the bridgeless network

--- Additional comment from lpeer on 2012-06-14 07:55:22 EDT ---

lowering priority and sevirity as the user can use the custom mode and configure any bond mode he wants.

Comment 1 Tim Hildred 2012-08-23 06:03:15 UTC
Added this to creating a bond device procedure:
"Bonding modes 1,2,4, and 5 can be selected. Any other mode can be configured using the <guilabel>Custom</guilabel> option."


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