Comment 9 for bug 1573264

So i was looking at the use of archdetect in etc/maas/templates/commissioning-user-data/snippets/maas_enlist.sh .
its used in 2 places
a.) get_host_architecture
  this i'm pretty sure can be replaced with dpkg --print-architecture
b.) get_host_subarchitecture
  here, archdetect is not used on i386|amd64|arm64|ppc64el)

So if this is only failing for you on arm64, then on arm64 you only ever use archdetecdt to get you the bit of information that could be provided by dpkg --print-architecture.

In cases where we do use archdetect to get the subarchitecture,
1.) i think that is limited to armhf
2.) i'm pretty sure we'll end up reporting invalid subarch in many cases. src/provisioningserver/drivers/__init__.py has a list of Architectures:
        amd64/generic
        arm64/generic
        arm64/xgene-uboot
        arm64/xgene-uboot-mustang
        armhf/generic
        armhf/highbank
        armhf/keystone
        i386/generic
        ppc64el/generic

Looking at libdebian-installer-0.102ubuntu1/debian/changelog it seems that archdetect now just returns 'generic' rather than 'highbank'. I think that is also the case on debian.

I might be missing something, but I'm pretty sure that this patch would work everywhere.