newly created LXD container has zero network devices
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Dimiter Naydenov |
Bug Description
Using:
$ juju version
2.0-beta4-
I bootstrap (xenial) on a node that has an interface (eth0) plus a number of VLANs:
$ maas maas nodes list | grep 192.168 | grep cidr | sort -u
"cidr": "192.168.10.0/24",
"cidr": "192.168.11.0/24",
"cidr": "192.168.12.0/24",
"cidr": "192.168.16.0/21",
"cidr": "192.168.24.0/21",
$ juju add-machine lxd:0
but the network profile for the container is missing all network devices.
$ sudo lxc profile show juju-machine-
name: juju-machine-
config: {}
description: ""
devices: {}
If instead you bootstrap and then immediately reboot the bootstrap node before adding the container you see the following (correct) configuration:
$ sudo lxc profile show juju-machine-
name: juju-machine-
config: {}
description: ""
devices:
eth0:
hwaddr: 00:16:3e:11:ab:ee
mtu: "1500"
name: eth0
nictype: bridged
parent: br-eth0
type: nic
eth1:
hwaddr: 00:16:3e:08:4b:d8
mtu: "1500"
name: eth1
nictype: bridged
parent: br-eth0.10
type: nic
eth2:
hwaddr: 00:16:3e:2b:76:cf
mtu: "1500"
name: eth2
nictype: bridged
parent: br-eth0.11
type: nic
eth3:
hwaddr: 00:16:3e:32:c5:3f
mtu: "1500"
name: eth3
nictype: bridged
parent: br-eth0.12
type: nic
eth4:
hwaddr: 00:16:3e:a4:52:9a
mtu: "1500"
name: eth4
nictype: bridged
parent: br-eth0.13
type: nic
eth5:
hwaddr: 00:16:3e:89:ed:fb
mtu: "1500"
name: eth5
nictype: bridged
parent: br-eth0.14
type: nic
This is potentially timing related because very occasionally I do see one network inteface added, typically the eth0 device.
Changed in juju-core: | |
assignee: | nobody → Andrew McDermott (frobware) |
Changed in juju-core: | |
status: | New → Triaged |
Changed in juju-core: | |
milestone: | none → 2.0-beta4 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
assignee: | Andrew McDermott (frobware) → Dimiter Naydenov (dimitern) |
tags: | added: conjure |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → In Progress |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0-rc1 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta5 → none |
milestone: | none → 2.0-beta5 |
Raising this to critical as the OpenStack folk have already bumped into this issue deploying charms via LXD.
<jamespage> frobware, lxd containers on machine 0 appear to be OK /bugs.launchpad .net/juju- core/+bug/ 1564395 /launchpad. net/bugs/ 1564395> pastebin. ubuntu. com/15567781/
<jamespage> just not on 1 and 2
<frobware> jamespage: aha.
<frobware> jamespage: you have run into https:/
<mup> Bug #1564395: newly created LXD container has zero network devices <bootstrap> <network> <juju-core:New> <https:/
<frobware> jamespage: which I raised about 30 mins ago
<frobware> jamespage: the containers on 1 have no network devices - http://