"juju storage-pools --provider=..." does not work correctly
Bug #1608821 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
I've just bootstrapped AWS with juju master (commit 313b1808637f2af
ERROR "ebs" not supported
This is clearly incorrect.
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 2.0-rc1 → 2.0.0 |
| Changed in juju-core: | |
| milestone: | 2.0.0 → 2.0-beta15 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta15 → none |
| milestone: | none → 2.0-beta15 |
To post a comment you must log in.
The filtering code was bogus, using model name where it should have been using the model's cloud provider type. If I create a new model called "ec2", then the command works as expected.