root-disk constraint broken on ec2
Bug #1324729 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Ian Booth | ||
| 1.18 |
Fix Released
|
Critical
|
Ian Booth | ||
Bug Description
From a user:
> Trying to deploy a charm with some extra root disk space. When using the root-disk constraint defined above I get the following error:
>
> '(error: no instance types in us-east-1 matching constraints "cpu-power=100 root-disk=16384M")'
>
> I’m deploying a bundle with the following constraints: constraints: "mem=4G arch=amd64”, but need more disk-space then the default provided.
It appears Juju is failing to successfully match the specified constraints to an available instance type in ec2 because the instance type entries have RootDisk set to 0 (the root disk size is dynamically allocated when the instance is started).
Related branches
lp:~wallyworld/juju-core/ec2-root-disk-constraint
- Juju Engineering: Pending requested
-
Diff: 64 lines (+7/-5)3 files modifiedenvirons/instances/instancetype.go (+1/-1)
environs/instances/instancetype_test.go (+0/-4)
provider/ec2/image_test.go (+6/-0)
lp:~wallyworld/juju-core/ec2-root-disk-constraint-1.18
- Juju Engineering: Pending requested
-
Diff: 64 lines (+7/-5)3 files modifiedenvirons/instances/instancetype.go (+1/-1)
environs/instances/instancetype_test.go (+0/-4)
provider/ec2/image_test.go (+6/-0)
| Changed in juju-core: | |
| milestone: | 1.19.3 → 1.19.4 |
| Changed in juju-core: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| importance: | Critical → High |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
