add-storage does not respect provider's maximum ranges
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
On the Azure provider, the VM instance types that Juju uses for its model-config default may only have 2 disks attached to them. Perhaps the maximum number of disks per instance type be added as a constraint?
$ juju deploy swift-storage
$ juju add-storage swift-storage/0 block-devices=
$ juju status --storage
Model Controller Cloud/Region Version SLA Timestamp
default c-teststorage azure/southeastasia 2.6.6.1 unsupported 14:07:21+12:00
App Version Status Scale Charm Store Rev OS Notes
swift-storage waiting 0/1 swift-storage jujucharms 256 ubuntu
Unit Workload Agent Machine Public address Ports Message
swift-storage/0* waiting allocating 0 52.139.235.153 agent initializing
Machine State DNS Inst id Series AZ Message
0 started 52.139.235.153 machine-0 bionic
Storage Unit Storage id Type Pool Mountpoint Size Status Message
swift-storage/0 block-devices/0 block azure-premium 1.0GiB attaching compute.
swift-storage/0 block-devices/1 block azure-premium 1.0GiB attaching compute.
swift-storage/0 block-devices/2 block azure-premium 1.0GiB attaching compute.
tags: |
added: azure-provider storage removed: stora |
Changed in juju: | |
status: | New → Triaged |
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.