[Bug 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10

[Stéphane Graber]

Just managed to reproduce it here, it's caused by Network Manager
deciding to mess with our bridge instead of leaving it alone as it
should.

Current workarounds include:
 - reboot
 - systemctl stop network-manager && systemctl restart lxc-net && systemct start network-manager

This only kicks in when the interface is brought up after network-
manager, so it doesn't affect boot since lxc-net starts before network-
manager and it doesn't affect upgrades where a container is already
running (as we don't destroy the bridge in that case).

But it does absolutely affect all new installs and upgrades done when no
container is running.

This is a critical regression in Network Manager behavior, NM should
NEVER touch non-physical interfaces and it should even less start
flushing existing network configuration.

Changes are this affects libvirt too, unless libvirt bring up takes long
enough to win the race against NM.

** Package changed: lxc (Ubuntu) => network-manager (Ubuntu)

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

** Changed in: network-manager (Ubuntu)
       Status: New => Triaged

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Critical
       Status: Triaged

** Also affects: network-manager (Ubuntu Wily)
   Importance: Undecided
       Status: New

** Changed in: network-manager (Ubuntu Wily)
       Status: New => Triaged

** Changed in: network-manager (Ubuntu Wily)
   Importance: Undecided => Critical

** Tags added: regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1512749

Title:
  lxcbr0 dissappears on Ubuntu 15.10

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