Open nbrys opened 4 years ago
That's strange. 10.0.0.6 is the IP the director should be on. Can you see a vm on that IP in the AWS console? Generally the upgrade would delete the director before trying to create it. Did this happen earlier in your deploy?
What version of Control Tower are you upgrading from and to?
I have a vm with that ip: bosh/0
I'm not very sure about the version we are upgrading from. We are running concourse 5.6.0. We are trying to upgrade to latest control tower release
When you run the deploy command do you see it deleting the existing director? Something like:
Started deploying
Waiting for the agent on VM 'vm-cf762ded-1163-411e-6481-ad0869ed5bd2'... Finished (00:00:00)
Stopping jobs on instance 'unknown/0'... Finished (00:00:01)
Unmounting disk 'disk-f54b86d9-6367-4c60-46f3-6b95dc2de995'... Finished (00:00:06)
Deleting VM 'vm-cf762ded-1163-411e-6481-ad0869ed5bd2'... Finished (00:00:50)
Because the built-in pipeline hangs i tried upgrading the environment from the cli: /control-tower-darwin-amd64 deploy --iaas aws --region eu-west-1 concourse-id
But i get the following error: