tools info mismatch on arch with lxd containers

[Martin Packman]

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://reports.vapour.ws/releases/3909/job/functional-container-networking-lxd/attempt/39>

    containers:
      0/lxd/0:
        juju-status:
          current: error
          message: tools info mismatch ({2.0-rc1-xenial-amd64 69d947975812b1f8bf6a15aef4f95e4a65f68bad618afa2bfe10a5a6aceb4289
            19790489}, {2.0-rc1-xenial-arm64 ce68f1658fb52bbbb874ec900fb5b4cd98023c4084ee9e5619f0a2ffe2d19b21
            18403876})
          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:
        juju-status:
          current: error
          message: tools info mismatch ({2.0-rc1-trusty-amd64 d0768bd1995317a4427a76c303c2e21ff5efe7026b728b681430525aa2945c3a
            19795496}, {2.0-rc1-trusty-ppc64el e9dba8fecb8921ffaca6c3d558beb886ca1773e79e228c2ab68e7b58c2f91d3f
            26377462})
          since: 20 Apr 2016 22:34:01Z

[Andrew Wilkins (axwalk)]

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.

[Andrew Wilkins (axwalk)]

Actually scratch that, apparently we don't support running i386 on amd64 (say). So host-arch filtering for all, then.

[Andrew Wilkins (axwalk)]

https://github.com/juju/juju/pull/5244