juju doesn't use maas' knowledge of system architecture when picking tools
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
When using maas as a provider, juju doesn't use maas' knowledge of the system architecture to pick the correct tools version.
For example, when bootstrapping with a constraint results in an armhf system being picked, amd64 tools are picked:
ubuntu@juju-dev:~$ juju bootstrap -v -v --constraints "tags=calxeda-
Launching instance
WARNING picked arbitrary tools &{"1.18.
If I supply an additional constraint of "arch=armhf", the correct tools version is picked:
ubuntu@juju-dev:~$ juju bootstrap -v -v --constraints "tags=calxeda-
Launching instance
WARNING picked arbitrary tools &{"1.18.
But, maas knows this system is armhf and therefore I shouldn't need to supply that myself as an additional constraint. This will result in non amd64 architectures not working unless special care is taken.
This affects 1.18.0-
tags: | added: server-hwe |
tags: | added: bootstrap maas-provider |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.19.0 |
tags: | added: arm64 ppc64el |
description: | updated |
description: | updated |
tags: | added: armhf-hwe |
Changed in juju-core: | |
milestone: | 1.19.0 → 1.19.1 |
Changed in juju-core: | |
milestone: | 1.19.1 → 1.20.0 |
Changed in juju-core: | |
milestone: | 1.20.0 → next-stable |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
I'm making some related changes, so will fix this while I'm there.