auto-compose LXD VM fails due to default root disk size "0" only when also specifying an extra storage disk
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
When using a MAAS LXD KVM host, charms with additional storage disks fail to deploy by default.
Example: juju deploy postgresql --storage pgdata=10G
This only fails when you are trying to automatically compose a VM, but it fails not because of the additional disk but due to the root-disk size being specified as "0".
If you over-ride the root-disk size by running "juju set-model-
For whatever reason the logic seems not to understand "0" as auto-allocate the size when there is an additional storage disk and it needs to compose a new VM.
The error is:
0 pending pending focal failed to start machine 0 (failed to acquire node: No available machine matches constraints: [('agent_name', ['6ca452ff-
MAAS 3.2.0-11989-
LXD 5.0.0-b0287c1
Can be reproduced with a MAAS lab setup as follows:
https:/
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.9.34 |
Changed in juju: | |
milestone: | 2.9.34 → none |
Changed in juju: | |
importance: | Low → Medium |
status: | Confirmed → Triaged |
This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.