Switch default instance type from m1.small to t2.small/m3.medium for EC2 provider
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Cheryl Jennings | ||
1.24 |
Fix Released
|
Critical
|
Cheryl Jennings | ||
1.25 |
Fix Released
|
High
|
Cheryl Jennings |
Bug Description
m1.small as the default instance size relies on the previous generation instance type [1]. Amazon is encouraging moving to current generation instance types. t2.small would be comparable to m1.small at half the price or m3.medium would provide consistent performance for a bit more. Either way, my testing is failing because capacity for m1.small is being exhausted.
$ juju charm test -e amazon-charmtest
juju-test INFO : Starting test run on amazon-charmtest using Juju 1.20.7
Launching instance
ERROR bootstrap failed: cannot start bootstrap instance: cannot run instances: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1d, us-east-1b. (InsufficientIn
Bootstrap failed, destroying environment
ERROR cannot start bootstrap instance: cannot run instances: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1d, us-east-1b. (InsufficientIn
juju-test.conductor WARNING : Could not bootstrap amazon-charmtest, got Bootstrap returned with an exit > 0. Skipping
Launching instance
ERROR bootstrap failed: cannot start bootstrap instance: cannot run instances: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1d, us-east-1b. (InsufficientIn
Bootstrap failed, destroying environment
ERROR cannot start bootstrap instance: cannot run instances: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1d, us-east-1b. (InsufficientIn
juju-test.conductor WARNING : Could not bootstrap amazon-charmtest, got Bootstrap returned with an exit > 0. Skipping
juju-test INFO : Results: 0 passed, 0 failed, 2 errored
[1] https:/
summary: |
- Switch default instance type from m1 to m3 for EC2 provider + Switch default instance type from m1.small to t2.small/m3.medium for EC2 + provider |
tags: | added: ec2-provider |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in juju-core: | |
milestone: | none → 1.25-beta1 |
milestone: | 1.25-beta1 → 1.26-alpha1 |
no longer affects: | juju-core/1.26 |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
assignee: | Nate Finch (natefinch) → Katherine Cox-Buday (cox-katherine-e) |
Changed in juju-core: | |
assignee: | Katherine Cox-Buday (cox-katherine-e) → Cheryl Jennings (cherylj) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
sigh.. agreed this should be t2.small/m3.medium but the issue on zone avail is separate and not related (and also filed separately).