[Bug 1073820] [NEW] ifdown/ifup of bond interface does not add slaves

[Ralf Spenneberg]

Public bug reported:

Release: Ubuntu 12.04
ifenslave-2.6                    1.1.0-19ubuntu5 

At boot time bonding interfaces are activated fine. But if I manually
ifdown the bonding interface and subsequently ifup it againt the
physical network cards are not enslaved.

I use the following configuration:
auto extern
iface extern inet static
        address 192.168.0.5
        netmask 255.255.255.0
        bond-mode 1
        bond-miimon 100
        bond-slaves none

auto eth0
allow-extern eth0
iface eth0 inet manual
        bond-master extern

auto eth2
allow-extern eth2
iface eth2 inet manual
        bond-master extern

Situation after boot:
# cat /proc/net/bonding/extern
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:26:2d:05:37:2f
Slave queue ID: 0

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:15:17:f6:ec:d9
Slave queue ID: 0

When issuing ifdown and subsequently ifup the following is displayed:
# ifup extern
Waiting for a slave to join extern (will timeout after 60s)
No slave joined extern, continuing anyway
Failed to bring up extern.

By the way, replacing extern with a typical bonding-device name as bond1
does not change the behaviour.

Adding 
bond-primary eth0 eth2 
to all stanzas does not change the behavior.

Changing bond-slaves to 
bond-slaves eth0 eth2
does not change the behaviour. README.Debian states that if both bond-master and bond-slaves is used bond-slaves is ignored.

The only way to correct the behaviour is to manually ifup eth0 and ifup eth2. I thought this is the responsibility of the 
allow-extern eth0/eth2
lines.

** Affects: ifenslave-2.6 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifenslave-2.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1073820

Title:
  ifdown/ifup of bond interface does not add slaves

Status in “ifenslave-2.6” package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 12.04
  ifenslave-2.6                    1.1.0-19ubuntu5 

  At boot time bonding interfaces are activated fine. But if I manually
  ifdown the bonding interface and subsequently ifup it againt the
  physical network cards are not enslaved.

  I use the following configuration:
  auto extern
  iface extern inet static
          address 192.168.0.5
          netmask 255.255.255.0
          bond-mode 1
          bond-miimon 100
          bond-slaves none

  auto eth0
  allow-extern eth0
  iface eth0 inet manual
          bond-master extern

  auto eth2
  allow-extern eth2
  iface eth2 inet manual
          bond-master extern

  Situation after boot:
  # cat /proc/net/bonding/extern
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: fault-tolerance (active-backup)
  Primary Slave: None
  Currently Active Slave: eth0
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  Slave Interface: eth0
  MII Status: up
  Speed: 1000 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:26:2d:05:37:2f
  Slave queue ID: 0

  Slave Interface: eth2
  MII Status: up
  Speed: 1000 Mbps
  Duplex: full
  Link Failure Count: 0
  Permanent HW addr: 00:15:17:f6:ec:d9
  Slave queue ID: 0

  When issuing ifdown and subsequently ifup the following is displayed:
  # ifup extern
  Waiting for a slave to join extern (will timeout after 60s)
  No slave joined extern, continuing anyway
  Failed to bring up extern.

  By the way, replacing extern with a typical bonding-device name as
  bond1 does not change the behaviour.

  Adding 
  bond-primary eth0 eth2 
  to all stanzas does not change the behavior.

  Changing bond-slaves to 
  bond-slaves eth0 eth2
  does not change the behaviour. README.Debian states that if both bond-master and bond-slaves is used bond-slaves is ignored.

  The only way to correct the behaviour is to manually ifup eth0 and ifup eth2. I thought this is the responsibility of the 
  allow-extern eth0/eth2
  lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/1073820/+subscriptions