MAAS Latest stable (ppa:maas/stable)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
Triaged
|
High
|
Unassigned |
Bug Description
Ubuntu: focal
When attempting to install the charm without passing any `maas_source` option it will fail.
It seems that `maas_source` should be made a `Required` option or at least have as a default ppa the latest version of maas i.e. ppa:maas/2.9
The stable ppa has being deprecated with result to break the `apt-get update` with the following error:
```
apt-get update
Hit:1 http://
Get:2 http://
Hit:3 http://
Ign:4 http://
Get:5 http://
Err:6 http://
404 Not Found [IP: 91.189.95.85 80]
Get:7 http://
Reading package lists... Done
E: The repository 'http://
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
```
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.