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

[Martin Pitt]

Moving to ifupdown. systemd does not configure the network (unless you
set them up in networkd, but we don't do that anywhere automatically and
there's no evidence that you did, and it's networking.service that
hangs).

I also don't see much wrong about this, except maybe that
interfaces.d/50-cloud-init.cfg and interfaces.d/eth0 both configure
eth0. But the latter (created by cloud-init I suppose) is a dead file as
/e/n/interfaces only includes *.cfg files, so that shouldn't matter.

** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)

** Summary changed:

- systemctl wants to configure interfaces it shouldn't (lxdbr0)
+ ifupdown wants to configure interfaces it shouldn't (lxdbr0)

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

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

Status in ifupdown package in Ubuntu:
  Confirmed
Status in lxd 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/ifupdown/+bug/1569064/+subscriptions