Re: Issue on re-deploy to AWS - static IP already reserved/in use

Home Messages Hashtags Subgroups

#71

Re: Issue on re-deploy to AWS - static IP already reserved/in use

Alexander Lomov #71 We had the similar issue with AWS. In AWS pannel we couldn't find any instance that used some IP address, still there was no ability to create an instance with such IP. We got this bug after we redeployed cluster several times. I think it could be AWS problem, so the solution here will be to put this IP addresses to the list of reserved IPs. ------------------------ Alex Lomov Altoros — Cloud Foundry deployment, training and integration Twitter: @code1n <https://twitter.com/code1n> GitHub: @allomov <https://gist.github.com/allomov> toggle quoted message Show quoted text On Thu, May 7, 2015 at 8:10 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: Was that IP previously assigned to a different VM (check via `bosh vms`)? Currently BOSH does not allow to pick a static IP if it's already in use by another VM. You could try putting it as a reserved IP, then doing bosh deploy, and then assigning it as a static IP for the haproxy VM. On Thu, May 7, 2015 at 3:32 AM, Lev Berman <lev.berman(a)altoros.com> wrote: Have you terminated the previous Amazon HA Proxy instance? If not, this might be the reason of the reserved IP error. On Thu, May 7, 2015 at 1:11 PM, teddyking <ed(a)cloudcredo.com> wrote: 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 -- Lev Berman Altoros - Cloud Foundry deployment, training and integration Github : https://github.com/ldmberman <https://github.com/ldmberman> _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh attachment.html
More All Messages By This Member

View All 8 Messages In Topic

#71

Join {cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.

Home Hashtags Subgroups Terms