Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Previously, VDSM failed to configure bonding mode until the network was restarted due to a change in the kernel semantics regarding asking for changes in bond mode. Now, the VDSM changes bond mode only when the bonding device is down, meaning the Red Hat Enterprise Virtualization Manager-configured bonding mode takes effect immediately.
Description of problem:
Configuring bonding interface via rhevm (vdsm) doesn't actually configure the bonding mode but only adding the slaves.
looks like bonding mode is the latest mode before the current configuration.
Steps to Reproduce:
1. check /proc/net/bonding/bond0
2. write down the "Bonding Mode:"
3. configure new bonding interface mode=4 (or any other mode - different then what exists) on same bond0
4. check /proc/net/bonding/bond0
Actual results:
/proc/net/bonding/bond0 will still contain the old "Bonding Mode:" instead of updating the new mode=4
Expected results:
update mode regarding configuration
Additional info:
** This bug appear also on latest 3.0.z (vdsm-4.9-113.2.el6_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
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
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