"juju deploy" does not validate volume/filesystem params
Bug #1501709 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
| juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
| 1.25 |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
When creating a storage pool, we validate the pool configuration. When we deploy, we constraints against the charm's storage requirements, and ensure that a suitable pool/provider has been requested. We don't, however, validate the volume/filesystem parameters (namely, size).
| Changed in juju-core: | |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Changed in juju-core: | |
| milestone: | 1.26-alpha1 → 1.26-alpha2 |
| Changed in juju-core: | |
| milestone: | 1.26-alpha2 → 1.26-beta1 |
| Changed in juju-core: | |
| milestone: | 1.26-beta1 → 2.0-alpha2 |
| Changed in juju-core: | |
| milestone: | 2.0-alpha2 → 2.0-alpha3 |
| Changed in juju-core: | |
| milestone: | 2.0-alpha3 → 2.0-beta4 |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| Changed in juju-core: | |
| assignee: | Andrew Wilkins (axwalk) → nobody |
| importance: | High → Medium |
| Changed in juju-core: | |
| milestone: | 2.0-beta4 → 2.1.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| milestone: | none → 2.1.0 |
| Changed in juju-core: | |
| status: | New → Won't Fix |
| Changed in juju: | |
| milestone: | 2.1-rc2 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This should be pretty easy to fix, but it's not high priority. Lowered importance to Medium.