lxd container fails to launch on bionic host: No associated target operation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips | ||
2.3 |
Fix Released
|
High
|
Joseph Phillips |
Bug Description
juju version: 2.4-beta2-
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:
https:/
machine-0.log from host:
https:/
host lxd.log:
https:/
host info:
ubuntu@
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@
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic
ubuntu@
3.0.0
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 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
May also be worth noting that both systemd-resolve and dnsmasq are listening:
https:/ /paste. ubuntu. com/p/35BnrvG7c m/
This also includes the config for dnsmasq (for lxd)