Charms with storage don't use cloud-native default if size is specified, but provider is omitted
Bug #1468153 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
If a charm specifies that it requires a filesystem with name "data", then the following should deploy the charm using the cloud's native filesystem or volume support:
juju deploy <charm> --storage data=1G
For example, on AWS this should deploy an instance, attach an EBS volume, and then create a filesystem on that volume. Right now it always uses the "rootfs" provider.
This can be worked around be explicitly specifying the provider/pool.
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
