tools info mismatch on arch with lxd containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
On master, trying to add or deploy into lxd containers in a cloud results in the lxd container juju agent going into error state due to an arch mismatch with tools.
<http://
containers:
0/lxd/0:
current: error
message: tools info mismatch ({2.0-rc1-
since: 20 Apr 2016 17:43:31Z
Note, amd64 != arm64. Another test, using a bundle defining lxd containers rather than "add-machine lxd:0" fails basically the same way:
1/lxd/0:
current: error
message: tools info mismatch ({2.0-rc1-
since: 20 Apr 2016 22:34:01Z
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
tags: | added: landscape |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta6 → none |
milestone: | none → 2.0-beta6 |
Neither the lxd nor kvm provisioner filters tools by arch, but lxc does. kvm should only filter if a constraint hasn't been specified, but lxd can only work with container=host arch.
Just running some live tests, then I need to fix unit tests.