Re: upgrade bosh director but got error message "IP in use"
should i actually remove the existing bosh director VM first at the IaaSlayer (i am using openstack), then run bosh-init?
to be explicit, no, you should not have to do this when migration happens.
On Sat, Feb 6, 2016 at 1:47 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:
Make sure to follow directions from:
http://bosh.io/docs/migrate-to-bosh-init.html. You should see bosh-init
find bosh-deployments.yml file and migrate it. If migration has succeeded
bosh-deployments.yml would have been removed. If it was not removed that
means you just installed a separate Director VM.
On Sat, Feb 6, 2016 at 1:29 PM, Jeff Han <hanzhefeng(a)gmail.com> wrote:Hi all,
i was trying to use bosh-init to upgrade my current running bosh
director to a newer stemcell, at the very last step when it's creating the
VM, it threw error and said: "...fixed ip address 192.168.1.11 is already
this is weird because i believe bosh-init should recreate the VM, migrate
the current content to the new VM and delete the old VM. why it's
complaining the old VM is using the fixed IP?
should i actually remove the existing bosh director VM first at the IaaS
layer (i am using openstack), then run bosh-init?