Comment 14 for bug 1923268

Unfortunately it appears this issue goes beyond just enlistment. I manually added 6 new arm64 systems using the MAAS UI, and made sure I set the architecture to "arm64/generic". They then automatically entered commissioning mode. However, they are also failing to Commission. MAAS shows "0/arm64" in the "CORES/ARCH" column, but MAAS' GRUB config still wants to provide them with x86 bits (see below). I was able to proceed by interactively editing the GRUB config on the console (s/amd64/arm64/g; s/(linux|initrd)efi/\1/) on each console. For some reason commissioning that way left the network unconfigured, so I then manually configured a NIC on each system, and then *re-*commissioned, which did work fine.

                             GNU GRUB version 2.04

 ����������������������������������������������������������������������������Ŀ
 �setparams 'Commission' �
 � �
 � echo 'Booting under MAAS direction...' �
 � linuxefi (http,10.229.32.21:5248)/images/ubuntu/amd64/ga-20.04/focal/s\�
 �table/boot-kernel nomodeset ro root=squash:http://10.229.32.21:5248/images/\�
 �ubuntu/amd64/ga-20.04/focal/stable/squashfs ip=::::maas-enlist:BOOTIF ip6=o\�
 �ff overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:\{'datasource_list': [\�
 �'MAAS']\}end_cc cloud-config-url=http://10.229.32.21:5248/MAAS/metadata/lat\�
 �est/enlist-preseed/?op=get_enlist_preseed apparmor=0 log_host=10.229.32.21 \�
 �log_port=5247 --- sysrq_always_enabled BOOTIF=01-${net_default_mac} �
 � initrdefi (http,10.229.32.21:5248)/images/ubuntu/amd64/ga-20.04/focal/s\�
 �table/boot-initrd �
 � �
 ������������������������������������������������������������������������������