bond_mode in /etc/network/interfaces ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifenslave-2.6 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Steve Langasek |
Bug Description
Binary package hint: ifenslave-2.6
In Karmic and Lucid the option bond_mode in /etc/network/
For example I have
auto bond2
iface bond2 inet static
slaves eth1 eth2
address 192.168.5.24
netmask 255.255.255.0
network 192.168.5.0
broadcast 192.168.5.255
bond_mode 5
But this gives me a mode 0 bond. I had to add 'options bonding mode=5' to /etc/modprobe.
SRU justification: the release notes and examples point users at the correct way to do it, but the README.Debian, which is usually the first place for experienced users to look, describes the wrong way to use the package. Since this is important enough to have in the release notes, it's also worth an SRU to update our other in-package documentation.
TEST CASE:
1. follow /usr/share/
2. reboot
3. observe that this fails to work
4. follow /usr/share/
5. reboot
6. confirm that this brings up a bonded interface
The patch is trivial and only affects documentation; the only regression potential is from latent rebuild bugs.
Changed in ifenslave-2.6 (Ubuntu Lucid): | |
importance: | Undecided → Medium |
assignee: | nobody → Steve Langasek (vorlon) |
description: | updated |
Changed in ifenslave-2.6 (Ubuntu Lucid): | |
status: | New → In Progress |
tags: |
added: verification-done removed: verification-needed |
Thank you for taking the time to report this issue and help to improve Ubuntu.
As documented at <https:/ /wiki.ubuntu. com/LucidLynx/ ReleaseNotes# Bonded% 20network% 20interfaces% 20must% 20use%20hotplug -style% 20configuration>, you must use the hotplug-style configuration in /etc/network/ interfaces; specifying the bond slaves in the bond interface stanza will not work. If you create the correct stanzas for eth1 and eth2, does this problem still occur?