touch-packages team mailing list archive

[MikeyB <michael@xxxxxxxxxxxxxxx>]

Looks like this also affects my configuration:
http://askubuntu.com/q/520051/9083

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1273201

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  I've created a bridge with network-manager-gnome, the bridge slave
  physical device is eth0. After a reboot the bridge is brought up, but
  eth0 isn't attached.

  First test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange!

  Second test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the "autoconnect" of the default wired network. After a reboot the bridge is brought up, but eth0 isn't  attached. Instead eth0 is brought up and full configured.

  After compiling and testing different upstream versions, i could track
  the problem down to bridge_ignore_without_connections.patch.  A
  network-manager package without this specific patch, brings my bridge
  up at boot and adds eth0 to the bridge in both test-cases.

  I've checked the behaviour on my ubuntu 13.10 box with network-manager
  (0.9.8.0-0ubuntu22)  and the trusty version network-manager
  (0.9.8.8-0ubuntu1) .

  Till now i couldn't  encounter any sideeffects of removing this patch
  with the bridge created by libvirt.

  Regards
  Mathias Kresin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions