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

Gareth Clay

Hi Dmitriy,

Thanks and sorry again for the slow response. Nabble stripped out my bosh vms output unfortunately - I’ve created a gist at <>

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.

Kind regards,

On 13 May 2015, at 6:13 pm, Dmitriy Kalinin <dkalinin(a)> wrote:

if you have specified your elastic IP in the manifest associated with a deployment job, BOSH will make sure it's connected and will not do any additional work on the subsequent deploys.

Btw I cannot see `bosh vms` output from your previous reply? Gist?

On Wed, May 13, 2015 at 3:11 AM, garethclay <gareth(a) <mailto:gareth(a)>> wrote:
Hi Dmitriy,

Thanks for the response and sorry for the slow reply! This is the output
from 'bosh vms' when we're in the EIP clash situation:

So it looks like BOSH knows that the HA proxy instance has already been
created and allocated the EIP. When we attempt the same deployment again, I
wondered if it would be possible for BOSH to determine 'okay, no work to do
here - this HA proxy instance is already in the state we want' and move on,
which is what it seems to do with instances which don't have EIPs attached?

Gareth and Ana

View this message in context: <>
Sent from the CF BOSH mailing list archive at
cf-bosh mailing list
cf-bosh(a) <mailto:cf-bosh(a)> <>

Join { to automatically receive all group messages.