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

[Martin Pitt]

So based on Serge's observation that removing
/etc/network/interfaces.d/* fixes this, and the log message

[CLOUDINIT] stages.py[INFO]: Applying network configuration from
fallback: {'version': 1, 'config': [{'name': 'lxdbr0', 'mac_address':
'fe:68:41:8c:e7:dc', 'subnets': [{'type': 'dhcp'}], 'type':
'physical'}]}

I suspect that cloud-init is adding a /etc/network/interfaces.d/
configuration for lxdbr0, which it shouldn't do?

** Changed in: lxd (Ubuntu)
       Status: Confirmed => Invalid

** Package changed: ifupdown (Ubuntu) => cloud-init (Ubuntu)

-- 
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 cloud-init package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid

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/cloud-init/+bug/1569064/+subscriptions