[Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Stéphane Graber]

Ok, the fact that this only happens when it does have an IP may point at
some kind of conflict.

Any chance you can (obviously before reboot), also post "ip addr show",
"ip route show" and the content of /etc/network/interfaces and any file
under /etc/network/interfaces.d/ ?

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m*     [0m] A start job is running for Raise network interfaces (32s / 5min 11s)[K[[0;1;31m*[0m[0;31m*    [0m]
   A start job is running for Raise network interfaces (33s / 5min 11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is running for Raise network interfaces (35
  s / 5min 11s)[K[    [0;31m*[0;1;31m*[0m] A start job is running for Raise network interfaces (36s / 5min 11s)[K[     [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 11s)[K[    [0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1569064/+subscriptions