When a custom image is updated it shows as synced before copied to rack controllers

MAAS bug-council,

This fix is desired on MAAS 3.0.

Once (and if) the MR to 3.4 is approved/merged, can we send backport MRs to 3.3/3.2? (And we'd follow with 3.1/3.0 as well, maintained by SEG.)

Thanks!

The advised way of dealing with updating images is to upload them with different names. The name of the image needs to be unique, because it's treated as an identifying property of an image, so having two images with different contents but the same name is not something that MAAS expects.

Having said that, it's not clear why the displayed state of image sync appears to be incorrect. This needs to be looked at first before we proceed with fixes.

Hi Jerzy,

> having two images with different contents but the same name is not something that MAAS expects.

Thanks for the clarification.

So, maybe should we change MAAS to error out image uploads with duplicate names?

(Or, alternatively, update the docs with this restriction? even though the command does suggest it performs a Create, not Update, operation: maas <profile> boot-resources create ..., IIRC).

IIUC, I think we should raise an error if the user tries to upload an image with a duplicated name.

Hi all,

To move this forward I can implement the raising of an error message or other behavior you see fit.

Thanks

This is something that clients quite often encounter. They delete a custom image and upload a new one with the exact same name only realizing later that the "new" image was never replicated to rack controllers as an image with the same name already existed on the filesystem.

Thank you,
Alan

We think there are two places where MAAS does not inform rack controller that the custom image has changed: the first when the image is deleted (MAAS should trigger rack controller sync, but currently does not), and the second where a new custom image is uploaded with the same name (MAAS DB trigger should fire, causing rack controller sync, but currently does not).

In MAAS 3.5 and later, the image storage and synchronisation mechanisms are significantly changed, so this issue is relevant to MAAS 3.4.x and earlier releases.