jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-1379) incompatible instance types selected in new AWS regions
Date Mon, 05 Feb 2018 13:26:01 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ignasi Barrera updated JCLOUDS-1379:
------------------------------------
    Labels: aws-ec2  (was: )

> incompatible instance types selected in new AWS regions
> -------------------------------------------------------
>
>                 Key: JCLOUDS-1379
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1379
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 2.0.3
>            Reporter: Alex Heneveld
>            Priority: Major
>              Labels: aws-ec2
>
> Using AWS EC2, if I specify minRam 4096M and minCores 4, I get a VM fine in some regions
(eu-west-1) but errors in others (eu-west-2)
> AWSResponseException: request POST https://ec2.eu-west-2.amazonaws.com/ HTTP/1.1 failed
with code 400, error: AWSError\{requestId='...', requestToken='null', code='Unsupported',
message='The requested configuration is currently not supported. Please check the documentation
for supported configurations.' ...}
> I assume this is because some instance types are not available in some regions.
> Can we do further filtering on instance type selection so that minRam/minCores work as
expected?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message