ppc64 architecture miss match for MAAS ppc64el

[Blake Rouse]

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

[Curtis Hovey (sinzui)]

Juju uses golang's naming conventions. Juju *should* map ppc64el to ppc64. Which version of Juju are you using?

This was a bug in Juju 1.18.x. where the wrong architecture was selected for some cloud providers. I closed the bug when manual-provider and local-kvm tests passed.

Since this issue was ambiguous a few months ago, the streams actually do contain ppc64el tools, but juju ignores them

[Blake Rouse (blake-rouse)]

What this tested on the MAAS provider? As a customer is seeing this issue with MAAS and Power8 hardware.

The version was newer than 1.18, I will have to check with the customer to get the exact version.

[Curtis Hovey (sinzui)]

There is/was no maas for ppc64 to test with. I am not aware there is a maas for ppc64 and that it support LE containers.

[Andres Rodriguez (andreserl)]

Hi Curtis,

MAAS Supports ppc64el in two cases:

1. PowerKVM (VM's under a PowerKVM can be managed via MAAS)
2. PowerNV (MAAS can install Ubuntu on a P8)

The one that's currently released in Trusty is (1)[0]. To test this, you;d need to have pre-created VM's and have MAAS manage this. Please, reach out to 'alai' on IRC to help you access the MAAS environment that you can test against.

Thanks.

[0]: https://launchpad.net/ubuntu/+source/maas/1.5.2+bzr2282-0ubuntu0.1

[Blake Rouse (blake-rouse)]

The version installed of JuJu 1.18.1-0ubuntu1.

[Curtis Hovey (sinzui)]

We may find this issue is fixed in 1.20. We need to test this.

[Robie Basak (racb)]

Removing the Ubuntu packaging task as it is pointless to have two people triage everything twice until we have verified the bug. Please re-add if necessary.

[Curtis Hovey (sinzui)]

This appears to be a mismatch between juju streams knowledge and image streams. the images streams have ppc64el. Note that tools streams are generated with ppc64 and pp64el have mappings to both because it wasn't clear to me which to use.

[Antonio Rosales (arosales)]

Andres/Blake,

On next reproduce could you provide the output of "juju bootstrap --debug"

-thanks,
Antonio

[Antonio Rosales (arosales)]

The MAAS access log may also be useful to determine what requests are being made.

-thanks,
Antonio

[Ian Booth (wallyworld)]

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".

[Dave Cheney (dave-cheney)]

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

[Andres Rodriguez (andreserl)]

ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64

Launching instance
ERROR bootstrap failed: cannot start bootstrap instance: cannot run instances: gomaasapi: got error back from server: 400 BAD REQUEST ({"arch": ["Architecture not recognised."]})
Bootstrap failed, destroying environment
ERROR cannot start bootstrap instance: cannot run instances: gomaasapi: got error back from server: 400 BAD REQUEST ({"arch": ["Architecture not recognised."]})

2 ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64el
error: invalid value "arch=ppc64el" for flag --constraints: bad "arch" constraint: "ppc64el" not recognized

2 ubuntu@landmaas:~⟫ juju bootstrap
Launching instance
WARNING picked arbitrary tools &{"1.18.4-trusty-amd64" "https://streams.canonical.com/juju/tools/releases/juju-1.18.4-trusty-amd64.tgz" "992e4244874ffec4af083cdeb58040420320f63ac6a3f7526c81d963fa4e53d6" %!q(int64=7389403)}
 - /MAAS/api/1.0/nodes/node-ab422cb2-1d8a-11e4-af09-e4115bb59c1e/
Waiting for address

[Andres Rodriguez (andreserl)]

with juju 1.19.4:

2 ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64
ERROR invalid constraint value: arch=ppc64
valid values are: [amd64]

[Andres Rodriguez (andreserl)]

update-alternatives: using /usr/lib/juju-1.20.1/bin/juju to provide /usr/bin/juju (juju) in auto mode
ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64el
error: invalid value "arch=ppc64el" for flag --constraints: bad "arch" constraint: "ppc64el" not recognized
2 ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64le
error: invalid value "arch=ppc64le" for flag --constraints: bad "arch" constraint: "ppc64le" not recognized
2 ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64
WARNING ignoring environments.yaml: using bootstrap config in file "/home/ubuntu/.juju/environments/maas.jenv"
debug2: channel 0: window 999379 sent adjust 49197
ERROR invalid constraint value: arch=ppc64 1‼ 7d1h 0.41 4x1.9GHz 1.9G64% 2014-08-06 17:12:18
valid values are: [amd64]

[Dave Cheney (dave-cheney)]

Thanks Andres. Clearly there is no intersection between the set of
architectures juju considers valid and the set that maas considers
valid.

On Thu, Aug 7, 2014 at 7:12 AM, Andres Rodriguez
<email address hidden> wrote:
> update-alternatives: using /usr/lib/juju-1.20.1/bin/juju to provide /usr/bin/juju (juju) in auto mode
> ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64el
> error: invalid value "arch=ppc64el" for flag --constraints: bad "arch" constraint: "ppc64el" not recognized
> 2 ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64le
> error: invalid value "arch=ppc64le" for flag --constraints: bad "arch" constraint: "ppc64le" not recognized
> 2 ubuntu@landmaas:~⟫ juju bootstrap --constraints arch=ppc64
> WARNING ignoring environments.yaml: using bootstrap config in file "/home/ubuntu/.juju/environments/maas.jenv"
> debug2: channel 0: window 999379 sent adjust 49197
> ERROR invalid constraint value: arch=ppc64 1‼ 7d1h 0.41 4x1.9GHz 1.9G64% 2014-08-06 17:12:18
> valid values are: [amd64]
>
> --
> 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

[Malte Menkhoff (mmenkhof)]

a customer has tested 1.20.5 and the problem is still existing:
root@pkvmc01:~# dpkg -l juju-core
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-===========================-==================-==================-===========================================================
ii juju-core 1.20.6-0ubuntu1~14 ppc64el Juju
is devops distilled - client

und habe einen bootstrap versucht: - aber so richtig erfolgreich war ich
damit nicht :-(((

root@pkvmc01:~# juju bootstrap --upload-tools=true --constraints
"tags=bootalt arch=ppc64el" --show-log --series=trusty
2014-09-03 20:15:05 INFO juju.cmd supercommand.go:37 running juju
[1.20.6-trusty-ppc64el gccgo]
Use of --series is deprecated. Please use --upload-series instead.
2014-09-03 20:15:06 INFO juju.utils http.go:59 hostname SSL verification
enabled
2014-09-03 20:15:06 INFO juju.utils http.go:59 hostname SSL verification
enabled
2014-09-03 20:15:06 INFO juju.utils http.go:59 hostname SSL verification
enabled
Bootstrap failed, destroying environment
2014-09-03 20:15:06 INFO juju.provider.common destroy.go:15 destroying
environment "maas"
2014-09-03 20:15:06 ERROR juju.cmd supercommand.go:323 invalid constraint
value: arch=ppc64el
valid values are: [i386 amd64]
root@pkvmc01:~# juju bootstrap --upload-tools=true --show-log
--upload-series=trusty
2014-09-03 20:16:00 INFO juju.cmd supercommand.go:37 running juju
[1.20.6-trusty-ppc64el gccgo]
2014-09-03 20:16:01 INFO juju.utils http.go:59 hostname SSL verification
enabled
2014-09-03 20:16:01 INFO juju.utils http.go:59 hostname SSL verification
enabled
2014-09-03 20:16:01 INFO juju.utils http.go:59 hostname SSL verification
enabled
2014-09-03 20:16:01 INFO juju.environs.bootstrap synctools.go:35 checking
that upload is possible
Bootstrap failed, destroying environment
2014-09-03 20:16:01 INFO juju.provider.common destroy.go:15 destroying
environment "maas"
2014-09-03 20:16:01 ERROR juju.cmd supercommand.go:323 environment "maas"
of type maas does not support instances running on "ppc64el"

could someone could be so fine and check if it is still a problem.