[
https://issues.apache.org/jira/browse/JCLOUDS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948585#comment-13948585
]
Andrew Phillips commented on JCLOUDS-515:
-----------------------------------------
Yes, this looks like it's happening when deserializing the return value. But if
that's true, then it would seem to be at odds with [~everett-toews]'s comment
that
> From create_volume.py we see that Cinder always sets the availability zone no
> matter what so
> this value should always be present when the create call is done.
Curious to see where the bug chips will fall!
> Cinder volume create does not require availability zone
> -------------------------------------------------------
>
> Key: JCLOUDS-515
> URL: https://issues.apache.org/jira/browse/JCLOUDS-515
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
> Affects Versions: 1.7.1
> Reporter: Jasdeep Hundal
> Assignee: Jasdeep Hundal
> Fix For: 1.8.0
>
>
> Openstack Cinder does not require specifying an availability zone for volume
> creation, but the Cinder API as implemented in JClouds does. We should change
> the check in the constructor of org.jclouds.openstack.cinder.v1.domain to
> allow a null value for availability zone.
> The docs on the v1 API are not readily available but tracing through the
> Cinder source code, we find this line that gets executed if we specify no
> availability zone in either the v1 or v2 block storage APIs:
> https://github.com/openstack/cinder/blob/master/cinder/volume/flows/api/create_volume.py#L247
> It can also be noted the the Block Storage v2 request here does not require
> an availability zone:
> http://docs.openstack.org/api/openstack-block-storage/2.0/content/POST_createVolume_v2__tenant_id__volumes_Volumes.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
