setting up container dependencies on host machine: not found

Bug #1738092 reported by David Ames
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Undecided
Unassigned

Bug Description

LXD containers are failing to come up with Juju 2.4-beta1 and MAAS 2.2.2

2017-12-13 22:15:46 WARNING juju.provisioner container_initialisation.go:135 not stopping machine agent container watcher due to error: setting up container dependencies on host machine: not found
2017-12-13 22:15:46 ERROR juju.provisioner container_initialisation.go:117 starting container provisioner for lxd: setting up container dependencies on host machine: not found
2017-12-13 22:15:46 ERROR juju.worker runner.go:392 exited "1-container-watcher": worker "1-container-watcher" exited: setting up container dependencies on host machine: not found
2017-12-13 22:15:50 WARNING juju.provisioner container_initialisation.go:135 not stopping machine agent container watcher due to error: setting up container dependencies on host machine: not found
2017-12-13 22:15:50 ERROR juju.provisioner container_initialisation.go:117 starting container provisioner for lxd: setting up container dependencies on host machine: not found
2017-12-13 22:15:50 ERROR juju.worker runner.go:392 exited "1-container-watcher": worker "1-container-watcher" exited: setting up container dependencies on host machine: not found

Revision history for this message
David Ames (thedac) wrote :

Machine log attached.

Revision history for this message
David Ames (thedac) wrote :

One more note. I am seeing this when deploying https://jujucharms.com/openstack-base/.

Just last week this was testing with no problem.

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

Not seen with the OpenStack provider.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

@David Ames (thedac),

Could you please provide a step-by-step scenario -what you have setup on MAAS side, what commands you ran on Juju side, how were you creating containers on Juju side (placement directives or another method)...

Changed in juju:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.