juju 2.0.2 bootstrap from amd64 to s390x manual host requires explicit arch=s390x

[Andrew McLeod]

Arch must be specified when bootstrapping with 2.0.2 on an amd64 host to an s390x manual host even though the bootstrap detects the archicture, e.g.:

(localhost is amd64, manual remote bootstrap host, 10.13.3.2, is s390x)

$ juju version
2.0.2-xenial-amd64

$ juju bootstrap manual/10.13.3.2 s390x --debug
...
02:17:57 INFO juju.environs.manual init.go:120 series: xenial, characteristics: arch=s390x cores=1 mem=1788M
...
02:17:57 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0.2 for amd64
...
02:18:00 ERROR cmd supercommand.go:458 failed to bootstrap model: no matching tools available

However, if "--constraints arch=s390x" is specified the bootstrap completes successfully.

debug log without constraints set:

(this command line forces agent version to 2.0.1 but same issue occured with no flags at all)
https://pastebin.canonical.com/174825/

debug log with constraints set:

https://pastebin.canonical.com/174826/

[Vance Morris (vmorris)]

I generally only bootstrap from s390x to s390x, but I can confirm that this is a problem.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.