brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Duncan Grant <>
Subject Re: AWS Fails to start
Date Thu, 16 Apr 2015 13:07:06 GMT
I'm getting the same error when I specify minRam 4096.  Dropping the minram
requirement fixes the problem (except I have a vm without enough ram).

My yaml looks like:

name: Empty large System
location: jclouds:aws-ec2:eu-west-1
- type: brooklyn.entity.basic.EmptySoftwareProcess
    minRam: 8192

And from the logs the template details are:

624314 2015-04-16 13:47:27,890 DEBUG b.l.jclouds.JcloudsLocation
[brooklyn-execmanager-eH5sU4JL-511]: jclouds found template
{image={id=eu-west-1/ami-3fcb5348, providerId=am       i-3fcb5348,
name=RightImage_CentOS_7.0_x64_v14.2.1_EBS, location={scope=REGION,
id=eu-west-1, description=eu-west-1, parent=aws-ec2, iso3166Codes=[IE]},
os={family=ce       ntos, arch=paravirtual, version=7.0,
is64Bit=true}, description=RightImage_CentOS_7.0_x64_v14.2.1_EBS,
 version=14.2.1_EBS, status=AVAILABLE[available], loginUser=root,
userMetadata={owner=411009282317, rootDeviceType=ebs,
virtualizationType=paravirtual, hypervisor=xen       }},
hardware={id=t2.medium, providerId=t2.medium, processors=[{cores=1.0,
speed=0.4}], ram=4096,
location={scope=REGION, id=eu-west-1, description=eu-west-1,
 parent=aws-ec2, iso3166Codes=[IE]}, options={userDataCksum=2f4a740b}}
(image {id=eu-west-1/ami-3fcb5348, providerId=ami-3fcb5348,
name=RightImage_CentOS_7.0_x64_v14.       2.1_EBS, location={scope=REGION,
id=eu-west-1, description=eu-west-1, parent=aws-ec2, iso3166Codes=[IE]},
os={family=centos, arch=paravirtual, version=7.0, descriptio
n=411009282317/RightImage_CentOS_7.0_x64_v14.2.1_EBS, is64Bit=true},
description=RightImage_CentOS_7.0_x64_v14.2.1_EBS, version=14.2.1_EBS,
status=AVAILABLE[available       ], loginUser=root,
userMetadata={owner=411009282317, rootDeviceType=ebs,
virtualizationType=paravirtual, hypervisor=xen}}) for provisioning in
JcloudsLocation[AWS Dub
lin:AKIAIKSCBKOOAXIOFYRA/aws-ec2:eu-west-1@uuGaPaUU] for

Could someone try the yaml above and see whether they have the same problem?

Also is there anything in the log that indicates what the problem is?



On 10 April 2015 at 18:41, Aled Sage <> wrote:

> Robert,
> There should be more info earlier in the log about the full jclouds
> "template" being used (including instance type, AMI, etc). Could you post
> that here please?
> If the "specified instance type" that has been auto-selected by
> brooklyn/jclouds now requires a VPC, then perhaps others can reproduce by
> explicitly choosing the same options as were in that template.
> Aled
> On 10/04/2015 13:14, Alex Heneveld wrote:
>> I've confirmed AWS is working as normal for me.
>> Robert, this suggests something with your local setup, or more worryingly
>> something with your account.  Could AWS have switched a default on some
>> accounts so that new machines require VPC and thus add'l setup to use
>> them?
>> Good to chase this down as if the latter it will affect people getting
>> started with Brooklyn.
>> Best
>> Alex
>> On 10 April 2015 at 10:32, Robert Moss <>
>> wrote:
>>  Hey,
>>> After pulling from master today, I am unable to deploy anything to AWS.
>>> My
>>> properties file is unchanged.
>>> Has anyone encountered this error before:
>>> Error invoking start at BasicApplicationImpl{id=QClWJ8Z3}: Error
>>> invoking
>>> start at MySqlNodeImpl{id=SbTHpjaK}:
>>> AWSResponseException:
>>> request POST HTTP/1.1 failed with
>>> code
>>> 400, error: AWSError{requestId='efe77bfa-b73d-40b2-82e2-8660492fb86b',
>>> requestToken='null', code='VPCResourceNotSpecified', message='The
>>> specified
>>> instance type can only be used in a VPC. A subnet ID or network interface
>>> ID is required to carry out the request.', context='{Response=,
>>> Errors=}'}
>>> Robert

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message