Closed drnic closed 9 years ago
As an aside, I looked up where the VM was and tried to document this in the manifest but same error:
resource_pools:
- name: default
network: default
cloud_properties:
instance_type: m3.large
availability_zone: us-east-1c
Actually I guess the problem is in reverse - the new VM was created in a different AZ from the original volume.
Yeah you have to specify availability_zone for VM, otherwise it can pop up in any AZ which will not match the persistent disk AZ. Same thing happens with the Director configuration.
Is this an unsolvable problem to pick an AZ internally and store it in deployments.json?
On Sun, Apr 19, 2015 at 5:44 PM, Dmitriy Kalinin notifications@github.com wrote:
Yeah you have to specify availability_zone for VM, otherwise it can pop up in any AZ which will not match the persistent disk AZ. Same thing happens with the Director configuration.
Reply to this email directly or view it on GitHub: https://github.com/cloudfoundry/bosh-init/issues/20#issuecomment-94329425
For now since availability zone is not a first class concept (proposal: https://github.com/cloudfoundry/bosh-notes/blob/master/availability-zones.md) we do not want to make IaaS specific knowledge in the IaaS agnostic part of the bosh-init.
Closing for now until AZs are a first class feature.
"The volume 'vol-968f7dd8' is not in the same availability zone as instance 'i-f95ed604'