Comment 6 for bug 1573264

I marked this 'wont fix' for maas-images.
MAAS sends the maas_enlist script to cloud-init to execute (etc/maas/templates/commissioning-user-data/snippets/maas_enlist.sh)
It is up to that program to make sure it can run. The images have not had archdetect in them for probably almost all of xenial cycle and probably part of wily.

The maas images now are exactly same content of cloud images and we dont want to change that. We also do not want to arbitrarily add packages to cloud images.

So, the suggestion i have is to have maas either
a.) work around this by implementing the same logic in that script that archdetect does (i suspect its fairly easily done with dpkg and some checks in /sys)
b.) install it if it is not there:
   which arch-detect || apt-get install archdetect || fail "sorry!"