Canonical Juju

m4 instance types not supported on AWS

Bug #1489477 reported by Marco Ceppi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Katherine Cox-Buday
Canonical Juju 2.0-alpha1
juju-core
Fix Released
High
Katherine Cox-Buday
1.25
Fix Released
High
Katherine Cox-Buday
juju-core 1.25-beta1

Bug Description

m4 are new instance types but not valid as constraints for instance-type on aws

$ juju deploy trusty/cassandra --constraints="instance-type=m4.xlarge" -n3
Added charm "cs:trusty/cassandra-3" to the environment.
ERROR invalid constraint value: instance-type=m4.xlarge valid values are: [m1.small m1.medium m1.large m1.xlarge 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]

https://aws.amazon.com/ec2/instance-types/#m3

Tested with juju 1.24.5 and verified on 1.25-alpha1 (master)

See original description
Marco Ceppi (marcoceppi)
description: updated
Marco Ceppi (marcoceppi)
description: updated
description: updated
Changed in juju-core:
status: New → Confirmed
description: updated
Curtis Hovey (sinzui)
tags: added: ec2-provider improvement
Changed in juju-core:
status: Confirmed → Triaged
importance: Undecided → High
milestone: none → 1.26.0
Katherine Cox-Buday (cox-katherine-e)
tags: added: feature
removed: improvement
Marco Ceppi (marcoceppi)
tags: added: benchmarking
Katherine Cox-Buday (cox-katherine-e)
Changed in juju-core:
assignee: nobody → Katherine Cox-Buday (cox-katherine-e)
status: Triaged → In Progress
Revision history for this message
Katherine Cox-Buday (cox-katherine-e) wrote :

Reviews underway:

1.25: http://reviews.vapour.ws/r/2717/

1.26: http://reviews.vapour.ws/r/2718/

Katherine Cox-Buday (cox-katherine-e)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Cheryl Jennings (cherylj)
Changed in juju-core:
milestone: 1.26.0 → 2.0-alpha1
Revision history for this message
Tom Barber (spicule) wrote :

I'm trying to launch m4.large with 2.0-alpha2 are m4.large not supported?

I see:

machine-0: 2016-02-14 19:48:26 ERROR juju.provisioner provisioner_task.go:654 cannot start instance for machine "4": no instance types in eu-west-1 matching constraints "instance-type=m4.large"

when trying:

juju deploy mysql --constraints="instance-type=m4.large"

in eu-west-1

Revision history for this message
Richard Harding (rharding) wrote :

It looks like the m4 sizes are in the ap-northeast and the eu-central, but not other regions.

https://github.com/juju/juju/blob/85d9f7bac87955ff8e204db671ac2f107426e99a/provider/ec2/instancetype.go#L481

It looks like they should be in all but two regions though. Just the south america and govt regions don't have the m4 types.

Canonical Juju QA Bot (juju-qa-bot)
affects: juju-core → juju
Changed in juju:
milestone: 2.0-alpha1 → none
milestone: none → 2.0-alpha1
Canonical Juju QA Bot (juju-qa-bot)
Changed in juju-core:
assignee: nobody → Katherine Cox-Buday (cox-katherine-e)
importance: Undecided → High
status: New → Fix Released
Revision history for this message
Joseph Borg (joeborg) wrote :

I believe this is still an issue in Juju.

I can launch m4.xlarge and p2.xlarge from the AWS interface, but I get the following error when trying with Juju:

ERROR cannot deploy bundle: cannot create machine for holding kubernetes-worker-cpu unit: cannot add a new machine: invalid constraint value: instance-type=m4.xlarge
valid values are: [m1.small cc2.8xlarge cr1.8xlarge g2.2xlarge r3.8xlarge i2.xlarge t1.micro c1.xlarge g2.8xlarge m3.xlarge m3.medium c3.4xlarge hs1.8xlarge r3.2xlarge m1.xlarge c3.xlarge c3.large c3.8xlarge r3.xlarge m2.xlarge m1.large i2.2xlarge i2.8xlarge cg1.4xlarge d2.2xlarge m2.2xlarge m3.2xlarge hi1.4xlarge m2.4xlarge r3.4xlarge r3.large d2.xlarge c1.medium d2.8xlarge m3.large m1.medium c3.2xlarge i2.4xlarge d2.4xlarge]

Is this a hardcoded list (I can't find it in the source code; only for the tests)? Or is it pulled from AWS?

Revision history for this message
John A Meinel (jameinel) wrote :

AWS provides a SKU file that has all of their instance types. However, it is a 120MB JSON file that is not reasonable to download live during a normal 'juju bootstrap'.
We currently compile that list into the source tree in provider/ec2/internal/ec2instancetypes

We need to update our normal release process to do that more frequently. There has also been a discussion of hosting a compressed/digested form on streams.canonical.com that would be reasonable to read more frequently, but it is a fair bit of work to get all of that working, so we haven't moved it forward yet.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

This specific bug has been fixed and released. I have created another bug to track the newly required update, bug # 1717181

Revision history for this message
Joseph Borg (joeborg) wrote :

 Could there a be a way to force that pull? IMO, that's better than blocking out instances entirely. I totally understand why downloading 120MB a time is a bad idea, but I think being able to force update on bootstrap is a good compromise.

p2.xlarge is also missing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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