Using the install_kvm API option during deployment does not make bionic the default
Bug #1797489 reported by
Mike Pontillo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
Currently, when using the install_kvm option to deploy a machine as a KVM pod, the default OS is used for deployment.
In the future, this could change to a new LTS release that hasn't been tested with the cloud-config we use for deploying KVM. This could cause security issues or break in other unexpected ways.
When users use the install_kvm option in the API, the default operating system/distro series should be defaulted to ubuntu/bionic.
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0rc2 |
Changed in maas: | |
milestone: | 2.5.0rc2 → 2.5.1 |
Changed in maas: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in maas: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in maas: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in maas: | |
milestone: | 2.5.4 → none |
summary: |
- [2.5] Using the install_kvm API option during deployment does not make - bionic the default + Using the install_kvm API option during deployment does not make bionic + the default |
To post a comment you must log in.
This is tricky because:
1. The default operating system may not be bionic, it may be Cosmic.
2. If you select an operating system specifically, like Cosmic, it should allow you to deploy a pod, although its probably not desired.