Update Machine API call fails if the image used to deploy the machine no longer exists

If one tries to update a pool or AZ, for example, on a deployed machine, and the image used to deploy the machine is no longer available, the update fails with something like

{\"distro_series\": [\"'custom/jammy-1' is not a valid distro_series.  It should be one of: 'custom/jammy-2', 'ubuntu/jammy', 'ubuntu/noble'.\"]}

forcing one to either keep all images ever deployed around forever, or hacking the database, or never updating a machine, or getting cute with naming and uploading images so they retain the same name (or maybe something else I haven’t yet thought of).

If this is by design, what is the reason? It seems a heavy burden to bear when the deployed image is not something one can Update anyway.

Should be related to Bug #2040324 “Power configuration change fails with <image> is n...” : Bugs : MAAS

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.