brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Heneveld (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-140) BrooklynImageChooser on EC2
Date Wed, 22 Apr 2015 08:31:58 GMT


Alex Heneveld commented on BROOKLYN-140:

confirmed, the bug is in jclouds.  it is setting the wrong virt type on many instance types.
 for these types the images passed to the BrooklynImageChooser are already filtered such that
*all* of them are incompatible.

i'm not seeing a workaround in brooklyn, except to pick instance types which support PV *and*
HVM.  see .

> BrooklynImageChooser on EC2 
> ----------------------------
>                 Key: BROOKLYN-140
>                 URL:
>             Project: Brooklyn
>          Issue Type: Improvement
>            Reporter: Andrea Turli
>            Assignee: Andrea Turli
>            Priority: Critical
> BrooklynImageChooser is not able to pick the right image on ec2 when a particular set
of hardwareSpec are specified and so
>  Error invoking start at EmptySoftwareProcessImpl{id=CHjSrqrz}:
request POST 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=}'}

This message was sent by Atlassian JIRA

View raw message