[jira] [Commented] (JCLOUDS-889) listImages don't consider `hvm` vs `paravirtual`

["Aled Sage (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498313#comment-14498313 ] 

Aled Sage commented on JCLOUDS-889:
-----------------------------------

For example, on aws-ec2 with minRam=8192, one of the images offered to the `TempateBuilder.imageChooser` was eu-west-1/ami-7db2d50a (a Canonical-published image for Ubuntu 14.04). The instance type inferred by jclouds was r3.large. However, this gave the error:

org.jclouds.aws.AWSResponseException: request POST
https://ec2.eu-west-1.amazonaws.com/ HTTP/1.1 failed with code 400, error:
AWSError{requestId='c72a6249-31b7-44c4-a30b-013527ebe249',
requestToken='null', code='InvalidParameterCombination',
message='Virtualization type 'hvm' is required for instances of type
'r3.large'.', context='{Response=, Errors=}'}


> listImages don't consider `hvm` vs `paravirtual`
> ------------------------------------------------
>
>                 Key: JCLOUDS-889
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-889
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.9.0
>            Reporter: Andrea Turli
>
> the node creation fails if one only specifies `osFamily` and `minRam=8G` (which triggers the creation of a large instance type) as `hvm` is an implicit requirement not satisfied by the templateBuilder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)