Comment 12 for bug 1349771

Related: https://bugs.launchpad.net/juju-core/+bug/1290654

On Thu, Aug 7, 2014 at 4:40 AM, Ian Booth <email address hidden> wrote:
> Juju looks for tools and images named after "ppc64" because that's what
> gccgo returns for the host architecture.
>
> The simplestreams image metatdata contains images for "ppc64el".
>
> So there's a mismatch there. It would be potentially difficult for Juju
> to deviate from "ppc64" since constraints for architectures expect
> "arch=pcc64" and changing this would deviate from the behaviour in
> trusty. Attempting to support "ppc64" for constraints and "ppc64el" for
> image/tools lookup just makes things confusing and error prone.
>
> I'm not sure whether simplestreams metadata should have followed Juju's
> lead and published data named after "ppc64". I think we should do as is
> done for tools metadata and publish simplestreams image metadata for
> both "ppc64" and "ppc64el".
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1349771
>
> Title:
> ppc64 architecture miss match for MAAS ppc64el
>
> Status in juju-core:
> Triaged
> Status in juju-core 1.20 series:
> Triaged
>
> Bug description:
> Deploying juju using MAAS on a Power8 system (ppc64el) reports a
> architecture miss match, saying ppc64 is not a valid architecture. The
> architecture for MAAS should be ppc64el, as that is the architecture
> for Ubuntu.
>
> The archive naming is:
>
> https://launchpad.net/ubuntu/trusty/ppc64el
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1349771/+subscriptions