Hi BOSH users!

We're running into an error when attempting to re-deploy a failing BOSH
deployment of CF to AWS:

`ha_proxy_z1/0' asked for a static IP 52.28.90.12 but it's already
reserved/in use

We're essentially doing the following:

* Allocate new EIP in AWS
* Generate manifest for CF with the EIP assigned to HA Proxy
* Run `bosh deploy` - this fails because we're hitting AWS API limits
* Run `bosh deploy` again - this now fails due to the above 'already
reserved' error

Is this the expected behaviour?
We've tried manually releasing the EIP in AWS and retrying the deployment,
but we still experience the 'already reserved' failure.

We're running BOSH version 1.2922.0 and have attached the relevant
backtrace
from the debug log.

Any help appreciated.
Thanks,
Ed and Gareth

aws-static-ip-already-reserved-debug.txt
<
http://cf-bosh.70367.x6.nabble.com/file/n10/aws-static-ip-already-reserved-debug.txt

--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/Issue-on-re-deploy-to-AWS-static-IP-already-reserved-in-use-tp10.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh