search

cloudfoundry / docs-deploying-cf

The docs repo for material on deploying Cloud Foundry
Apache License 2.0
15 stars 101 forks source link

Error 100: Can't use multiple availability zones #5

Closed sfielder closed 10 years ago

sfielder commented 10 years ago

Followed instructions located at http://docs.cloudfoundry.org/deploying/ec2/bootstrap-aws-vpc.html and during deployment received the following exception.

Either there is a step missing in the documentation to update the availability zones or there is an issue with the manifest generator which produces this file.

Could someone please help me with a fix and clarification on why I received this error? Thank you

screen shot 2014-03-15 at 6 43 51 am

cf-gitbot commented 10 years ago

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: http://www.pivotaltracker.com/story/show/67599698

mstine commented 10 years ago

I ran into a similar error a few weeks ago, posting my resolution below. Make sure this isn't what's happening to you:

Root cause identified...copy-paste bug.

Here's my bosh_environment:

... export BOSH_AWS_REGION=us-east-1 export BOSH_VPC_SECONDARY_AZ=us-east-1b # see note below export BOSH_VPC_PRIMARY_AZ=us-east-1d # see note below

Here's the relevant section of cf-aws-stub.yml:

availability_zone: us-east-1b # Change this if you'd like to availability_zone2: us-east-1d # Change this if you'd like to subnet_ids: cf1: subnet-22c8e964 cf2: subnet-5f0c4c77

So...notice that in bosh_environment, the AZ's are listed secondary then primary. In the stub they are listed primary then secondary.

Easy to see where I went wrong huh?

Matt Stine | Platform Engineer, Cloud Foundry | Pivotal 901-493-5546 | Skype: mstine1978 | mstine@goPivotal.com

goPivotal.com

On Sat, Mar 15, 2014 at 5:51 AM, sfielder notifications@github.com wrote:

Followed instructions located at http://docs.cloudfoundry.org/deploying/ec2/bootstrap-aws-vpc.html and during deployment received the following exception.

Either there is a step missing in the documentation to update the availability zones or there is an issue with the manifest generator which produces this file.

Could someone please help me with a fix and clarification on why I received this error? Thank you

[image: screen shot 2014-03-15 at 6 43 51 am]https://f.cloud.github.com/assets/737626/2428138/e8d39bec-ac2e-11e3-9693-9ba452da4156.png

Reply to this email directly or view it on GitHubhttps://github.com/cloudfoundry/docs-deploying-cf/issues/5 .

sfielder commented 10 years ago

Thanks @mstine
I had the same issue with my config. Do I also need to swap the cf1 and cf2 subnets? Also given the changes (very newb to cloudfoundry) where should I pick up from the installation instructions to deploy successfully?

Really appreciate your help!

mstine commented 10 years ago

As long as your cf1 and cf2 subnets match up with your AZ's, you'll be OK. Just make sure they're not transposed.

Once you fix that, re-source your bosh_environment and run "bosh deploy" again. It ought to resolve things.

Let me know if you run into additional problems.

Matt Stine | Platform Engineer, Cloud Foundry | Pivotal 901-493-5546 | Skype: mstine1978 | mstine@goPivotal.com

goPivotal.com

On Mon, Mar 17, 2014 at 2:39 PM, sfielder notifications@github.com wrote:

Thanks @mstine https://github.com/mstine

I had the same issue with my config. Do I also need to swap the cf1 and cf2 subnets? Also given the changes (very newb to cloudfoundry) where should I pick up from the installation instructions to deploy successfully?

Really appreciate your help!

Reply to this email directly or view it on GitHubhttps://github.com/cloudfoundry/docs-deploying-cf/issues/5#issuecomment-37860583 .

animatedmax commented 10 years ago

With PR #37, we've updated the bootstrap-aws-vpc.html document by swapping the values in the bosh_environment file.