OpenStack AZ Cinder Volumes Not Working

Rupak Ganguly

2014-08-20 04:36:09 UTC

Jisaac,
If I remember correctly, the cinder volumes have to be on the same
availability zone as the nova server you are attaching the volume to.

Can you check that they are both using the same availability zone?

Thanks,
Rupak Ganguly

On Aug 19, 2014, at 1:02 PM, Jisaac <jc-WDK53C2pZtRWk0Htik3J/***@public.gmane.org> wrote:

Were attempting to get a working CloudFoundry deployed via Micro Bosh,
which relies on Fog, within a non default availability zone and are
failing at attaching the cinder volume. Fog, via micro bosh, is deploying
the instance within the correct availability zone but the cinder volumes
are not. Fog is instead using the default AZ, nova, to create the Cinder
volumes and thus why we are unable to attach the disk to the instance once
the disk is created. It would appear that we are running up agasinst this
bug within fog https://github.com/fog/fog/issues/3011 . Since Bosh's CPI
relies on fog, i'm curious as if anyone has run into this and/or could
provide suggestions to workaround this issue?

--
You received this message because you are subscribed to the Google Groups
"ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ruby-fog+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ruby-fog+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/d/optout.