Comment 1 for bug 1909122

Note: affects deployments with ocf:maas resources on Focal and later (which is, obviously, now, a more frequent target).

Workaround (as implied in the report by the OP) is to set the maas_source option to "stable/<version>" in the deployment bundle to match the version of MaaS that it is being deployed to.

Fix is to (on focal+) check whether it is default, and block if it is not set and an osf:maas resource is detected. Relevant search in 'hook.py' is to search for 'ocf:maas' and trace the called functions.