Public bug reported:

I configured a container as follows, using some bridges (virbr0 and
virbr1, my NAT network and test network, respectively) that I had
previously configured in libvirt:

lxc init ubuntu-daily:b bionic-maas2 -p '' -s default
lxc network attach virbr0 bionic-maas2 eth0 eth0
lxc network attach virbr1 bionic-maas2 eth1 eth1
lxc config set bionic-maas2 user.network-config "version: 2
ethernets:
  eth0:
    match:
      name: eth0
    dhcp4: true
  eth1:
    match:
      name: eth1
bridges:
  br0:
    interfaces: [eth1]
"
lxc start bionic-maas2
lxc exec bionic-maas2 bash

After executing the shell, I noticed that the bridge interface I
specified had been created, but not brought online:

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: br0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
    link/ether c6:0d:b9:b9:68:44 brd ff:ff:ff:ff:ff:ff
32: eth0@if33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
    link/ether 00:16:3e:2d:b9:df brd ff:ff:ff:ff:ff:ff link-netnsid 0
34: eth1@if35: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master 
br0 state UP mode DEFAULT group default qlen 1000
    link/ether 00:16:3e:ef:4a:5b brd ff:ff:ff:ff:ff:ff link-netnsid 0

# networkctl
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 br0              ether              off         unmanaged 
 32 eth0             ether              routable    configured
 34 eth1             ether              carrier     configured

To work around the issue, I had to manually set the link up:

# ip link set dev br0 up

# networkctl
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 br0              ether              degraded    unmanaged 
 32 eth0             ether              routable    configured
 34 eth1             ether              carrier     configured

4 links listed.

It doesn't really seem useful for netplan to configure a 'bridge
interface but not set it to come online.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cloud-init 17.2-30-gf7deaf15-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Fri Feb  9 01:29:50 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
user_data.txt:
 #cloud-config
 {}

** Affects: netplan
     Importance: Undecided
         Status: New

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic uec-images

** Also affects: netplan
   Importance: Undecided
       Status: New

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

Title:
  Bridges fail to come online when configured via LXD, netplan, and
  cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1748332/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to