NetworkManager reverts all bond modes to balanced-rr

[Christopher Edwards]

Description: Ubuntu 13.04
Release: 13.04

network-manager:
  Installed: 0.9.8.0-0ubuntu6
  Candidate: 0.9.8.0-0ubuntu6
  Version table:
 *** 0.9.8.0-0ubuntu6 0
        500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

I am attempting to use the new bonding interface in NetworkManager in 13.04. NetworkManager will not write any other mode than "Round-robin" to the configuration file.

For example I can choose "Active Backup" when editing the bond, save and close the NetworkManager. When I open it again, the mode is once again set to "Round-robin" and not my previously checked "Active Backup" when I closed NetworkManager.

Also if I edit "/etc/NetworkManager/system-connections/Bond\ Connection\ 1" by hand to have any other mode, NetworkManager resets the value on open of the application.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Thu May 9 18:53:36 2013
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-10-02 (219 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
IpRoute:
 default via ###.###.###.### dev bond0 proto static
 ###.###.###.###/24 dev bond0 proto kernel scope link src ###.###.###.### metric 5
 169.254.0.0/16 dev eth0 scope link metric 1000
MarkForUpload: True
NetDevice.bonding_masters:
 Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: device path not found

 X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:

SourcePackage: network-manager
UpgradeStatus: Upgraded to raring on 2013-05-09 (0 days ago)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 bond0 slave 2 9fb3fe4a-b24f-4a97-84d6-b72bf7c3d8e3 802-3-ethernet 1368150838 Thu 09 May 2013 06:53:58 PM PDT yes no /org/freedesktop/NetworkManager/Settings/2
 MSFF 6e10a816-5b2a-4e88-93c5-bf70483fe6a5 vpn 1360882873 Thu 14 Feb 2013 03:01:13 PM PST no no /org/freedesktop/NetworkManager/Settings/1
 Bond connection 1 57d726f0-663a-40f5-86da-96befb80dd77 bond 1368150838 Thu 09 May 2013 06:53:58 PM PDT yes no /org/freedesktop/NetworkManager/Settings/0
 bond0 slave 1 55b7fab4-00bd-4468-bcbf-123cfd12bcc8 802-3-ethernet 1368150838 Thu 09 May 2013 06:53:58 PM PDT yes no /org/freedesktop/NetworkManager/Settings/3
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth1 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/2
 bond0 bond connected /org/freedesktop/NetworkManager/Devices/1
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Emily Loebl (mloebl)]

Does anyone know a good work around? If I manual edit the config file for bond0 in /etc/NetworkManager/system-connections and set it to mode=802.3ad or mode=4, it keeps the change (obviously until I try to make a change in NetworkManager again), however interface is still set to round-robin regardless:
cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Thanks!

[Christopher Edwards (csedwar)]

Basically my way around it was to disable network manager (https://help.ubuntu.com/community/NetworkManager - scroll down to disabling network manager). Then I followed these instructions (https://help.ubuntu.com/community/UbuntuBonding)

I had attempted this previously without disabling network manager and would get to a point where I needed the network to be enabled during boot before login, which was not happening when using the combination of ifneslave with networkmanager. Basically as far as I could tell, they were fighting over who was managing networking. This was causing all kinds of login/home directory mounting issues.

[Mathieu Trudel-Lapierre (cyphermox)]

Tentatively confirming; though I'll take a look at how NM creates the bond to see whether it actually supports any other option than RR. Setting to Triaged/Medium, we'll want to fix this if it's broken; though I'll need to bring up the bug upstream.

[Emily Loebl (mloebl)]

I am still seeing this in 13.10 as well.

[Emily Loebl (mloebl)]

Just installed a VM with the current 14.04 Beta that has NetworkManager 0.9.8.8 and it looks like the settings may be retained now (looks like may have been fixed in NM 0.9.8.4 looking at the release notes.)

[Emily Loebl (mloebl)]

Looking better:
cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

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

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
bond bond0 has no active aggregator

[Emily Loebl (mloebl)]

I just upgraded to 14.04, and can confirm I can configure thru Network Manager LACP and appears to be functioning correctly. I am no longer forced to use Round Robin