Comment 14 for bug 1420049

That is because machine-0 is amd64, tools selection must be fixated on
that version even though constraints force the provider to create
ppc64le machines.

On Thu, Feb 12, 2015 at 12:22 PM, Tim Penhey <email address hidden> wrote:
> Actually it looks like the LXC container is being started with amd64
> tools, not power ones. This is an issue.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1420049
>
> Title:
> ppc64el - jujud: Syntax error: word unexpected (expecting ")")
>
> Status in juju-core:
> Triaged
> Status in juju-core 1.21 series:
> Triaged
> Status in juju-core 1.22 series:
> Triaged
>
> Bug description:
> jujud: Syntax error: word unexpected (expecting ")")
>
> When deploying to ppc64el-hosted lxc containers, with the bootstrap
> node being amd64, all lxc units timeout in a pending state.
>
> Inspection of juju unit logs in each lxc container show only the following in each:
> /var/lib/juju/tools/machine-1-lxc-1/jujud: 1: /var/lib/juju/tools/machine-1-lxc-1/jujud: Syntax error: word unexpected (expecting ")")
>
> See http://paste.ubuntu.com/10145407/ for 1 entire unit log.
>
> The use case is:
> We have one service which needs to be on amd64, one service which needs to be on ppc64el natively, and several services which need to be in lxc containers on the ppc64el host. Namely, using ppc64el as the nova-compute and OpenStack api services node, and the amd64 node for bootstrap + neutron-gateway.
>
> The same bundle and charms deploy successfully when both hosts are
> amd64.
>
> See attached additional info.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1420049/+subscriptions