availability zone is ignored when creating volume

[dennis-sig]

It seems that Fog ignores the value of the availability_zone parameter when creating OpenStack volumes. In https://github.com/fog/fog/blob/master/lib/fog/openstack/models/compute/volume.rb line 28 I would expect this argument to be passed to the create_volume call, but it's not.

If this is by design, for example because there are problems with the OpenStack API when using this feature, it should be documented; but I would currently consider this a bug.

[geemus]

@krames @elight - could one of you take a look? Thanks!

[krames]

@geemus sure! I will add it to my todos.

[jclendennen]

We are also seeing this issue. The instance is created on the correct AZ, but the persistence volumes are not.

[elight]

@geemus you'll want to stop adding me to these and instead just add @smashwilson.

On Mon, Aug 18, 2014 at 7:08 PM, jclendennen notifications@github.com
wrote:

We are also seeing this issue. The instance is created on the correct AZ, but the persistence volumes are not.

Reply to this email directly or view it on GitHub:
#3011 (comment)

[geemus]

@elight k.

[rupakg]

@dennis-sig I am curious and wanted to ask you what behavior you see when you create a volume and pass it an availability zone? The volume is not created or is created on a diff. Availability zone. Are you specifically calling volume.create? Can you try the equivalent request method create_voloume directly to see what behavior that exhibits?

Sorry too many questions as I cannot get to code right now.

[grosskop]

@rupakg the behavior is that the volume is created in the default availability zone. If the compute node is created in another zone, it is not possible to attach the volume

[plribeiro3000]

Closing in favor of fog/fog-openstack#40