artful+ container on xenial host network fails to start

Bug #1752476 reported by Chris Sanders on 2018-03-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Witold Krecicki
2.3
High
Witold Krecicki

Bug Description

Juju: 2.3.4
MAAS: 2.3.0
LXD: 2.0.11

Deploying a xenial based host (GA or HWE kernel) fails to start containers when targeted with artful services. The container never leaves the starting state and checking on the host it's because it never brings up a network interface.

This is very easy to reproduce, deploy a Xenial host and then target the Ubuntu charm with a series of artful to a container on the machine.

I believe this is juju not supporting the netplan network which is now default in artful+. I can SSH to the machine and create a LXD image with LXC with "lxc launch ubuntu:artful" which launches as expected.

Additionally by logging into the container which is stuck and checking the interface, ifupdown isn't installed and no /etc/netplan files are created.

I'm not sure what other logging I can provide, it's very easy to reproduce and if any log files would be helpful I can get those as well.

Witold Krecicki (wpk) on 2018-03-02
Changed in juju:
importance: Undecided → High
assignee: nobody → Witold Krecicki (wpk)
status: New → In Progress
John A Meinel (jameinel) on 2018-03-05
Changed in juju:
milestone: none → 2.4-beta1
John A Meinel (jameinel) on 2018-03-26
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers