lxd container fails to launch on bionic host: No associated target operation

Bug #1765571 reported by Andrew McLeod on 2018-04-20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Joseph Phillips
Joseph Phillips

Bug Description

juju version: 2.4-beta2-xenial-amd64 (also tested, with the same results, on arm64 and ppc64el, using agent-stream devel, with the same versions of software)

concerns either a xenial lxd container or a bionic lxd container on a bionic (18.04) host

short error:

0/lxd/0 down pending bionic No associated target operation

juju status:


machine-0.log from host:


host lxd.log:


host info:

ubuntu@node-victor:~$ uname -a
Linux node-victor 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@node-victor:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic

ubuntu@node-victor:~$ lxd --version

Andrew McLeod (admcleod) wrote :

May also be worth noting that both systemd-resolve and dnsmasq are listening:


This also includes the config for dnsmasq (for lxd)

Andrew McLeod (admcleod) wrote :

Also, although there is already an lxdbr0 (some init has happened), I can't manually launch a container on this host (there is only the default profile in lxd profile list):

ubuntu@node-victor:/var/log$ sudo lxc launch ubuntu:
Creating the container
Error: Failed container creation: No storage pool found. Please create a new storage pool.

now "lxd launch ubuntu:" works.

juju add-unit -n1 --to lxd:0 ends up with a new error:

0/lxd/2 down pending xenial failed to start machine 0/lxd/2 (LXD error: No root device could be found.), retrying in 10s (9 more attempts)

Ian Booth (wallyworld) on 2018-04-27
Changed in juju:
milestone: none → 2.4-beta2
assignee: nobody → Joseph Phillips (manadart)
importance: Undecided → High
status: New → Triaged
Changed in juju:
status: Triaged → In Progress
Joseph Phillips (manadart) wrote :

PR is proposed for this; will be fixed when it lands:

Changed in juju:
status: In Progress → Fix Committed
Sean Feole (sfeole) wrote :

verified that this is now working in juju 2.4 beta2

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