Bug 1233035

Summary:	Change the default bonding mode to safe defaults (active-backup)
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Fabian Deutsch <fdeutsch>
Component:	ovirt-node	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED ERRATA	QA Contact:	wanghui <huiwa>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	cshao, danken, gklein, huiwa, leiwang, lsurette, melewis, yaniwang, ycui, ykaul
Target Milestone:	ovirt-3.6.1	Keywords:	ZStream
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-node-3.3.0-0.4.20150906git14a6024.el7ev	Doc Type:	Bug Fix
Doc Text:	Previously, creating a new bond used the balance-rr mode by default and this could lead to connection issues. Now, active-backup mode is used by default for newly created bonds as active-backup mode does not increase the available bandwidth but is safe to use in any setup.	Story Points:	---
Clone Of:
Clones:	1294340 (view as bug list)		Environment:
Last Closed:	2016-03-09 14:31:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1294340

Description Fabian Deutsch 2015-06-18 06:09:37 UTC

Description of problem:
Previously balance-rr was used as the default bonding mode. But this could lead to problems with Vm networks, especially during the hosted-engine setup. To prevent this problems (bug 1230638).

The default should be active-backup which is a safe start.

Comment 2 wanghui 2015-10-29 09:56:08 UTC

Test version:
rhev-hypervisor7-7.2-20151025.0.el7ev
ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch

Test steps:
1. Clean install rhev-hypervisor7-7.2-20151025.0.el7ev
2. Create bond and check the default mode

Test result:
1. After step2, it gives "mode=active-backup miimon=100" as the default options.

So this issue is fixed in ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch. Change the status to verified.

Comment 5 errata-xmlrpc 2016-03-09 14:31:23 UTC

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-0378.html