Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1294340

Summary:	[z-stream clone - 3.5.7] Change the default bonding mode to safe defaults (active-backup)
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-node	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED ERRATA	QA Contact:	wanghui <huiwa>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	cshao, danken, fdeutsch, gklein, huiwa, leiwang, lsurette, mburman, melewis, yaniwang, ycui, ykaul
Target Milestone:	ovirt-3.5.8	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, when setting up a bonded device the bond device was using a bonding mode, balance-rr, that was not suitable for all use cases. Now, safe bonding mode defaults, active-backup, are used so that the bonding mode is suitable for all regular use cases, including hosted engine.	Story Points:	---
Clone Of:	1233035	Environment:
Last Closed:	2016-02-29 14:51:04 UTC	Type:	---
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:	1233035
Bug Blocks:

Comment 3 wanghui 2016-02-03 03:08:04 UTC

Test version:
rhev-hypervisor7-7.2-20160128.1
ovirt-node-3.2.3-31.el7.noarch
rhev-hypervisor6-6.7-20160128.0
ovirt-node-3.2.3-31.el6.noarch

Test steps:
1. Clean install rhev-hypervisor7-7.2-20160128.1/rhev-hypervisor6-6.7-20160128.0
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.2.3-31.el7.noarch and ovirt-node-3.2.3-31.el6.noarch. Change the status to verified.

Comment 5 errata-xmlrpc 2016-02-29 14:51:04 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-0316.html