Created attachment 599788 [details]
vdsm 3.0 log

Created attachment 599789 [details]
vdsm 3.1 log

3.1 details:
kernel 2.6.32-286.el6.x86_64
libvirt-0.9.10-21.el6_3.1.x86_64
vdsm-4.9.6-21.0.el6_3.x86_64


3.0 details:
2.6.32-278.el6.x86_64
vdsm-4.9-113.2.el6_3.x86_64
libvirt-0.9.10-21.el6_3.3.x86_64

Your 3.1 kernel is older than your 3.0's. There's probably a place for upgrade.

Could you see when this was introduced? I mean, did it work fine with rhel-6.2? Please record initscripts and kernel versions.

The following patch by Mark Wu aims to fix this issue
http://gerrit.ovirt.org/6217

On rhel 6.2 with vdsm vdsm-4.9-113.1.el6.x86_64 it works fine. See more details below:

[root@dell-r210ii-08 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.2 (Santiago)

[root@dell-r210ii-08 ~]# uname -a
Linux dell-r210ii-08.rhev.lab.eng.brq.redhat.com 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

root@dell-r210ii-08 ~]# rpm -qa | grep vdsm
vdsm-4.9-113.1.el6.x86_64
vdsm-cli-4.9-113.1.el6.x86_64


[root@dell-r210ii-08 ~]# cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Aggregator selection policy (ad_select): stable
bond bond1 has no active aggregator

Slave Interface: p1p1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:04:28:b8
Aggregator ID: N/A
Slave queue ID: 0

Slave Interface: p1p2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:04:28:b9
Aggregator ID: N/A
Slave queue ID: 0

[root@dell-r210ii-08 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE=bond1
ONBOOT=yes
BOOTPROTO=none
BRIDGE=NET1
BONDING_OPTS=mode=4

Adding to above comment
# rpm -q initscripts
initscripts-9.03.27-1.el6.x86_64

I'd like to copy Mark's gerrit comment to here:

It turns out that it caused by a recent kernel change as you guessed. So that means this problem could only happen on fedora host, which explains that it's not reported before.

For details, please see the following kernel commit:

$git show 4a8bb7e2
commit 4a8bb7e27fbb68da888b55f26defd2855225b2d5
Author: Veaceslav Falico <vfalico>
Date: Tue Nov 15 06:44:42 2011 +0000

bonding: Don't allow mode change via sysfs with slaves present

When changing mode via bonding's sysfs, the slaves are not initialized
correctly. Forbid to change modes with slaves present to ensure that every
slave is initialized correctly via bond_enslave().

Signed-off-by: Veaceslav Falico <vfalico>
Signed-off-by: Andy Gospodarek <andy>
Acked-by: Nicolas de Pesloüan <nicolas.2p.debian>
Signed-off-by: David S. Miller <davem>

diff --git a/drivers/net/bonding/bond_sysfs.c b/drivers/net/bonding/bond_sysfs.c
index 5a20804..4ef7e2f 100644
--- a/drivers/net/bonding/bond_sysfs.c
+++ b/drivers/net/bonding/bond_sysfs.c
@@ -319,6 +319,13 @@ static ssize_t bonding_store_mode(struct device *d,
goto out;
}

+ if (bond->slave_cnt > 0) {
+     pr_err("unable to update mode of %s because it has slaves.\n",
+     bond->dev->name);
+     ret = -EPERM;
+     goto out;
+ }
+
new_value = bond_parse_parm(buf, bond_mode_tbl);
if (new_value < 0) {
pr_err("%s: Ignoring invalid mode value %.*s.\n",
[mark@localhost net]$ git name-rev --tag 4a8bb7e27fbb68da888b55f26defd2855225b2d5
4a8bb7e27fbb68da888b55f26defd2855225b2d5 tags/v3.2-rc3~25^2~4

*** Bug 832758 has been marked as a duplicate of this bug. ***

verify on vdsm-4.9.6-24.0.el6_3.x86_64 - PASS
i have configured all supported bond 1,2,4,5 and mode was updated.

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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html