© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
The issue is, currently from MAAS' perspective, a custom image really is a custom version of the supported Operating Systems - such as CentOS, RHEL and Ubuntu.
This was not the case with MAAS 2.9 and older, which let clients upload anything they wanted - ToasterOS FWIW - as "custom" and let MAAS happily deploy them.
This has changed since MAAS 3.0 with the introduction of extra validations for "custom" images, which kind of kills the entire point of having the "custom" option available.
The above hack works and lets you bypass the check when a custom image is uploaded while omitting the base_image parameter, but I ultimately believe this is something that needs to be fixed / reverted in the source code.
I understand we are not in a position of dictating any development policies to the MAAS team - but at the end of the day is is not a big ask and is simply something that will make a lot of users who rely on the custom image functionality much happier.
Thank you.