Juju won't let me use some instance types on AWS

Bug #1535838 reported by Chris MacNaughton
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Andrew Wilkins
juju-core
Won't Fix
Undecided
Unassigned
1.25
Won't Fix
Undecided
Unassigned

Bug Description

ERROR invalid constraint value: instance-type=d2.8xlarge
valid values are: [m1.small m1.medium m1.large m1.xlarge m4.large m4.xlarge m4.2xlarge m4.4xlarge m4.10xlarge m3.medium m3.large m3.xlarge m3.2xlarge c1.medium c1.xlarge cc2.8xlarge c3.large c3.xlarge c3.2xlarge c3.4xlarge c3.8xlarge cg1.4xlarge g2.2xlarge m2.xlarge m2.2xlarge m2.4xlarge cr1.8xlarge r3.large r3.xlarge r3.2xlarge r3.4xlarge r3.8xlarge hi1.4xlarge i2.xlarge i2.2xlarge i2.4xlarge i2.8xlarge hs1.8xlarge t1.micro t2.micro t2.small t2.medium c4.large c4.xlarge c4.2xlarge c4.4xlarge c4.8xlarge]

Tags: ateam
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

Juju version: 1.25.0-elcapitan-amd64

Revision history for this message
Cheryl Jennings (cherylj) wrote :

For posterity, can you also include what region you're using?

Changed in juju-core:
status: New → Triaged
Revision history for this message
Cheryl Jennings (cherylj) wrote :
Changed in juju-core:
importance: Undecided → High
milestone: none → 1.25.4
milestone: 1.25.4 → 2.0-alpha3
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote : Re: [Bug 1535838] Re: Juju won't let me use some instance types on AWS

Region is US East

> On Jan 19, 2016, at 18:12, Cheryl Jennings <email address hidden> wrote:
>
> For posterity, can you also include what region you're using?
>
> ** Changed in: juju-core
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535838
>
> Title:
> Juju won't let me use some instance types on AWS
>
> Status in juju-core:
> Triaged
> Status in juju-core 1.25 series:
> Triaged
>
> Bug description:
> ERROR invalid constraint value: instance-type=d2.8xlarge
> valid values are: [m1.small m1.medium m1.large m1.xlarge m4.large m4.xlarge m4.2xlarge m4.4xlarge m4.10xlarge m3.medium m3.large m3.xlarge m3.2xlarge c1.medium c1.xlarge cc2.8xlarge c3.large c3.xlarge c3.2xlarge c3.4xlarge c3.8xlarge cg1.4xlarge g2.2xlarge m2.xlarge m2.2xlarge m2.4xlarge cr1.8xlarge r3.large r3.xlarge r3.2xlarge r3.4xlarge r3.8xlarge hi1.4xlarge i2.xlarge i2.2xlarge i2.4xlarge i2.8xlarge hs1.8xlarge t1.micro t2.micro t2.small t2.medium c4.large c4.xlarge c4.2xlarge c4.4xlarge c4.8xlarge]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1535838/+subscriptions

Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta3
Revision history for this message
Nick Veitch (evilnick) wrote :

Related to this, that list is wrong anyhow. You can ask for but won't get e.g. a t2.medium

Possibly related to changes in t2 types - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-instances.html#t2-instances-vpc-support

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta3 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.0
affects: juju-core → juju
Changed in juju:
milestone: 2.0.0 → none
milestone: none → 2.0.0
Changed in juju-core:
status: New → Won't Fix
Revision history for this message
Anastasia (anastasia-macmood) wrote :

From Uros:

Controllers are CPU bounded, more cores you throw at them, more users they can handle, linear scalability. I'd really like us to have support for big cpus, both on aws and on gce.

Revision history for this message
Andrew Wilkins (axwalk) wrote :

I've updated our instance types, and D2 is in there now for 2.0. I need to make a fixes related to T2 and other instance types, so that they're only made available if you're in a VPC account.

Changed in juju:
status: Triaged → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Andrew Wilkins (axwalk)
Changed in juju:
status: In Progress → Fix Committed
tags: added: ateam
Curtis Hovey (sinzui)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.