Date
1 - 2 of 2
bosh-init deploy to AWS problems
Sean Dowd <ssdowd@...>
We are trying to do a bosh-init deploy bosh.yml onto AWS (using http://bosh.io/docs/init-aws.html) and keep getting this as a result:
Command 'deploy' failed: Deploying: Creating instance 'bosh/0': Creating VM: Creating vm with stemcell cid 'ami-5728e73c light': CPI 'create_vm' method responded with error: CmdError{"type":"Unknown","message":"The subnet ID 'subnet-135e0b76' does not exist","ok_to_retry":false} But subnet-135e0b76 clearly exists (it's visible via the AWS console and via 'aws ec2 describe-subnets'). The availability zone (us-west-2a) also matches bosh.yml. "Subnets": [ { "VpcId": "vpc-92cb8ff7", "Tags": [ ... ], "CidrBlock": "10.0.0.0/24", "MapPublicIpOnLaunch": false, "DefaultForAz": false, "State": "available", "AvailabilityZone": "us-west-2a", "SubnetId": "subnet-135e0b76", "AvailableIpAddressCount": 251 }, Any suggestions? |
|
Dmitriy Kalinin
Make sure to set `region` configuration (See
toggle quoted message
Show quoted text
http://bosh.io/docs/init-aws.html for an example manifest with region set). It defaults to us-east-1. Yours should be us-west-2. Also make sure to bosh-init delete if this is a new environment before setting the region in the manifest since bosh-init already imported stemcell into us-east-1 -- Creating vm with stemcell cid 'ami-5728e73c light' ( http://thecloudmarket.com/image/ami-5728e73c--bosh-d5ed0258-80f7-4514-a195-eff206e90c41#/definition ). On Mon, Sep 14, 2015 at 4:04 PM, sean d <ssdowd(a)gmail.com> wrote:
We are trying to do a bosh-init deploy bosh.yml onto AWS (using |
|