TestContainerStartedAndStopped cannot create mock container on ppc64el/arm64 xenial/wily
Bug #1550770 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Cheryl Jennings | ||
juju-core |
Fix Released
|
High
|
Cheryl Jennings | ||
1.25 |
Fix Released
|
High
|
Cheryl Jennings |
Bug Description
As seen at
http://
1.25 and several 2.0 branches cannot create a mock container to test lxc. This issue affects the minority series-archs. arm64 and ppc64el (on both wily and xenial), and centos7-amd64 fail.
Changed in juju-core: | |
assignee: | nobody → Cheryl Jennings (cherylj) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
tags: | added: 2.0-count |
tags: | removed: 2.0-count |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta2 → none |
milestone: | none → 2.0-beta2 |
Changed in juju-core: | |
assignee: | nobody → Cheryl Jennings (cherylj) |
importance: | Undecided → High |
status: | New → Fix Released |
To post a comment you must log in.
This test fails on centos because of the losetup / path issue:
[LOG] 0:10.940 ERROR juju.container.lxc failed to detach loop devices from lxc container: listing loop devices: exec: "losetup": executable file not found in $PATH
It fails on other series /arches because it cannot find tools to start the container with:
[LOG] 0:06.101 ERROR juju.provisioner cannot start instance for machine "0/lxc/0": need tools for arch arm64, only found [amd64]
This happens because we seed the tools with the current series / arch, but use the default series when creating a container ("trusty"). We need to add the trusty tools for the current arch.