Comment 3 for bug 1711154

I can't say for sure what was wrong in this case, but my guess is that you were using a pre-release of the Juju client, for which it checked official sources for the agent binaries, but couldn't find them. Juju then falls back to trying to upload a local copy of the agent binaries, but we only provide the binaries for the architecture that you are on.

If you use the final released versions of the Juju client, it should be able to find any binaries across all supported architectures.

You would still need to supply '--arch=XXX' if the desired target architecture is not the same as your local client architecture.