Regarding the 404's from not being able to D/L the image after it is created. If I copy the failed '/MAAS/images-stream/custom/...' URL out of the logs and try to wget it I also get a 404.
If I use 'maas-region dbshell --installed' to remove "custom/" from the bootresource's name:
UPDATE "maasserver_bootresource" SET "name" = 'coreos' WHERE ("maasserver_bootresource"."name" = 'custom/coreos' AND "maasserver_bootresource"."architecture" = 'amd64/generic');
Then I can use the same URL that had just 404'ed to successfully manually D/L the image. Of course that breaks the web interface (and from what I can see on the half broken interface it hasn't actually gotten rid of the 'out-of-sync' message) so it doesn't really get me into a usable state.
So AFAICT seems to be a disconnect between image storage and image download regarding how the names of custom images are special.
Regarding the 404's from not being able to D/L the image after it is created. If I copy the failed '/MAAS/ images- stream/ custom/ ...' URL out of the logs and try to wget it I also get a 404.
If I use 'maas-region dbshell --installed' to remove "custom/" from the bootresource's name:
UPDATE "maasserver_ bootresource" SET "name" = 'coreos' WHERE ("maasserver_ bootresource" ."name" = 'custom/coreos' AND "maasserver_ bootresource" ."architecture" = 'amd64/generic');
Then I can use the same URL that had just 404'ed to successfully manually D/L the image. Of course that breaks the web interface (and from what I can see on the half broken interface it hasn't actually gotten rid of the 'out-of-sync' message) so it doesn't really get me into a usable state.
So AFAICT seems to be a disconnect between image storage and image download regarding how the names of custom images are special.