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 [email protected]. For more options, visit https://groups.google.com/d/optout.
