PPC64, i386, and armhf systems fail commissioning due to architecture mismatching

As you pointed out this is a mismatch between how architectures are represented. There are three sets architecture naming schemes, Linux kernel, Debian, and Go. The Go architecture naming scheme is similar to Debian but as you found out its not exact. Below is my understanding of how architectures should map, however I've asked the kernel team for some clarification.

Kernel/LXD Debian Go
i686 i386 386
x86_64 amd64 amd64
aarch64 arm64 arm64
ppc64le ppc64el ppc64le
s390x s390x s390x
armv7l armhf arm

From this you can see MAAS is currently broken on i386, ppc64el, and armhf.

@MAAS engineering - We used archdetect because we use it during enlistment. I think we should standardize the Go binaries on the kernel naming scheme so we can use arch as Frank suggested. This will fix this bug and remove a dependency during commissioning.

I think it would make more sense to align with the Debian architectures, since that's what we use of the images. Having different names for the same architecture across MAAS will be confusing.

+1, we can just change the makefile target that generates the resources
binaries to output names that match Debian architectures.

On Mon, Apr 6, 2020 at 11:26 AM Björn Tillenius <email address hidden> wrote:

> I think it would make more sense to align with the Debian architectures,
> since that's what we use of the images. Having different names for the
> same architecture across MAAS will be confusing.
>
> --
> You received this bug notification because you are subscribed to MAAS
> Project.
> Matching subscriptions: MAAS Project
> https://bugs.launchpad.net/bugs/1870583
>
> Title:
> PPC64, i386, and armhf systems fail commissioning due to architecture
> mismatching
>
> Status in MAAS:
> Confirmed
> Status in MAAS 2.7 series:
> Confirmed
> Status in The Ubuntu-power-systems project:
> New
>
> Bug description:
> While trying to commission an OpenPower (P8) system on MAAS 2.7.0
> ('server teams maas server'), commissioning step
> 50-maas-01-commissioning fails with log:
>
> --2020-04-03 15:59:25--
> http://10.245.71.3:5248/machine-resources/ppc64el
> Connecting to 10.245.71.3:5248... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2020-04-03 15:59:25 ERROR 404: Not Found.
>
> Manually trying http://10.245.71.3:5248/machine-resources/ppc64le works
> and a download starts.
> (Notice the difference 'el' and 'le')
>
> Since I currently cannot connect to the OpenPower system (gulpin) where
> this occurs.
> I used a different P8 system and got this archdetect and arch output:
>
> $ archdetect
> ppc64el/chrp_ibm
> $ arch
> ppc64le
> $
>
> 'archdetect' on maas server:
> $ archdetect
> amd64/generic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1870583/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; status=Confirmed; importance=Critical;
> assignee=None;
> Launchpad-Bug: product=maas; productseries=2.7; status=Confirmed;
> importance=Critical; assignee=None;
> Launchpad-Bug: product=ubuntu-power-systems; status=New;
> importance=Undecided; assignee=maas;
> Launchpad-Bug-Tags: ppc64el
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: bjornt fheimes ltrager
> Launchpad-Bug-Reporter: Frank Heimes (fheimes)
> Launchpad-Bug-Modifier: Björn Tillenius (bjornt)
> Launchpad-Message-Rationale: Subscriber (MAAS Project)
> Launchpad-Message-For: ack
> Launchpad-Subscription: MAAS Project
>

--
Alberto Donato | <email address hidden>
https://launchpad.net/~ack | GPG: 2048R/9E2823B3

> From this you can see MAAS is currently broken on i386, ppc64el, and armhf.

It's worth noting that in src/provisioningserver/refresh/node_info_scripts.py:128 we have

BINARY="$(archdetect | cut -d '/' -f1 | sed 's/i386/386/g')"

so the important part thing is Debian matching "Go", and due to the sed, think we do work on (i)386