Region Controller import progress not available in 1 API request

[Jason Hobbs]

We had a test run last night that didn't complete import into the region after 25 minutes or so, it usually completes in 2 minutes. I can't tell if it made any progress and was just slow, or it never started or what. I want to add logging so I can see how far along it is, but I don't see how to do this via the API. Maybe I'm just missing it, but I want to be able to see something like % downloaded for each image that is being imported, or at least an overall % for all images.

[Andres Rodriguez (andreserl)]

boot-resources read shows what's currently imported, but does not show what's in progress nor what's queued for download:

http://paste.ubuntu.com/25240576/

[Blake Rouse (blake-rouse)]

If you use "boot-resource read" on each boot-resource you will get the information you are looking for. Queued images also show up in the list.

[Andres Rodriguez (andreserl)]

This is a valid bug that needs addressing because:

1. Using "boot-resource read" requires you to pass an ID of the specific boot resource.
2. Using "boot-resources read" to obtain such ID is impossible, provided that such endpoint only lists *synced* items.

So effectively, "boot-resources" read should show what's queue'd and the progress, because without that, we cannot use "boot-resource".

[Jason Hobbs (jason-hobbs)]

boot-resources read does list items that are both complete and incomplete:

http://paste.ubuntu.com/25240683/

But there is no indication of which items are complete or incomplete, so you would have to make a bunch (we have 53 boot resources) of additional API calls to find the information.

It would be a lot easier/faster if boot resources read gave progress information, or at least 'complete'/'incomplete'.

[Blake Rouse (blake-rouse)]

@Andres,

You are mixing the type from the status. SYNCED is the type of resource, meaning it is synced from simplestreams. All resources are shown in in the list whether they are queued, downloading, or complete.

@Jason,

I agree that would be an improvement, so its only 1 API call. That is the bug, but its still is possible to do today.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

[Björn Tillenius (bjornt)]

I can confirm that this is an issue, I'v also run into it from time to time. We might want to look into having code that detects that an image sync is stuck.