list-boot-images reports synced after only syncing bootloader/uefi for arm64

[Jason Hobbs]

maas is telling me my arm64 images are synced, but they really aren't.

After updating my boot-source-selections to include arm64 images for xenial, starting a boot-resource import, waiting for is-importing to go from True to False, and for my rack controller to go from 'syncing' to 'synced', my rack controller only as uefi/bootloader for arm64, not ubuntu/xenial:

https://pastebin.canonical.com/p/b7KXHR6JgF/

When I tried to enlist nodes, arm64 nodes failed to enlist and I got this error in regiond.log:

regiond.log:django.core.exceptions.ValidationError: ['xenial has no kernels available.']

90 minutes later when I went to debug this run, the ubuntu/xenial images for arm64 were there:

https://pastebin.canonical.com/p/FprKzWNhBy/

An amd64 VM node enlisted/commissioned without error.

This is with maas 2.3.2-6485-ge93e044-0ubuntu1~16.04.1.

[Andres Rodriguez (andreserl)]

While we investigate the issues, please try one of these options:

# This is what we currently do in the MAAS CI.
1. stop image import
2. add boot selections (e.g. arm64)
3. restart image import

or:

1. wait for amd64 images to be imported
2. add boot selections for arm64
3. start image import again.

[Jason Hobbs (jason-hobbs)]

Using 'boot-resources stop-import' before starting our arm64 import let us progress past this.