Re: Issue on re-deploy to AWS - static IP already reserved/in use
Hi Dmitriy,toggle quoted message Show quoted text
Thanks and sorry again for the slow response. Nabble stripped out my bosh vms output unfortunately - I’ve created a gist at https://gist.github.com/spikymonkey/9938dcdcc7a9a6097183 <https://gist.github.com/spikymonkey/9938dcdcc7a9a6097183>
It sounds like the behaviour you described is exactly what we want. It seems though that we’ve hit a case where BOSH can’t determine that it has no additional work to do, and so goes off to do it again. This fails because the EIP connection has already been done on the first deployment attempt.
On 13 May 2015, at 6:13 pm, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: