Juju does not support current AWS instance types

Bug #1754735 reported by Daniel Amaya
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
John A Meinel
2.3
Fix Released
High
John A Meinel

Bug Description

I'm using juju 2.3.4:
[root@data juju-bin]# juju version
2.3.4-centos7-amd64

Attempted to deploy to instance-type x1e.4xlarge and received the following error:

[root@data juju-bin]# juju deploy redis --constraints "spaces=igw instance-type=x1e.4xlarge"
Located charm "cs:trusty/redis-0".
Deploying charm "cs:trusty/redis-0".
ERROR cannot add application "redis": invalid constraint value: instance-type=x1e.4xlarge
valid values are: [c5.xlarge c5.large t2.medium t2.nano m1.medium r4.large c5.2xlarge x1.32xlarge c4.4xlarge t2.2xlarge h1.2xlarge g3.16xlarge m1.xlarge c4.xlarge i3.4xlarge c1.xlarge m2.2xlarge c3.large cc2.8xlarge g2.8xlarge r3.large i3.2xlarge r4.2xlarge m5.24xlarge r4.8xlarge c3.4xlarge i2.4xlarge c3.xlarge d2.2xlarge i2.8xlarge m4.large m4.4xlarge d2.4xlarge m3.2xlarge m1.large m1.small hs1.8xlarge d2.8xlarge m3.large m5.12xlarge h1.4xlarge r4.16xlarge c3.2xlarge r4.xlarge h1.8xlarge r3.2xlarge m4.2xlarge m3.medium r3.4xlarge c4.large x1e.32xlarge m2.xlarge r3.xlarge c3.8xlarge m4.10xlarge t2.micro i2.xlarge r3.8xlarge c1.medium f1.16xlarge m5.2xlarge p2.8xlarge cr1.8xlarge g2.2xlarge m2.4xlarge c5.4xlarge i3.8xlarge m5.4xlarge x1e.xlarge r4.4xlarge m5.xlarge m4.16xlarge c5.18xlarge c4.8xlarge m3.xlarge m5.large c5.9xlarge i3.large p3.16xlarge t2.large f1.2xlarge m4.xlarge t2.small t1.micro c4.2xlarge p2.xlarge d2.xlarge p2.16xlarge g3.4xlarge g3.8xlarge p3.8xlarge x1.16xlarge t2.xlarge i3.16xlarge p3.2xlarge h1.16xlarge i3.xlarge i2.2xlarge]

John A Meinel (jameinel)
Changed in juju:
assignee: nobody → John A Meinel (jameinel)
importance: Undecided → High
status: New → In Progress
milestone: none → 2.4-beta1
Revision history for this message
John A Meinel (jameinel) wrote :
Revision history for this message
John A Meinel (jameinel) wrote :

After regenerating the data, it seems that we've supported several of the x1e.* instance types in us-east-1, but they've added more. Also, c5 and m5 have been added to other regions (us-west-1), and some other changes like a new region (ap-northeast-3), though supporting that needs more than just the patch I put together.

Revision history for this message
John A Meinel (jameinel) wrote :
Changed in juju:
status: In Progress → Fix Committed
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.