[
https://issues.apache.org/jira/browse/DTACLOUD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510853#comment-13510853
]
Joseph J. VLcek commented on DTACLOUD-390:
------------------------------------------
I'm not sure if I'm reproducing this correctly.
I do see the diagnostic from "p opts" output as you describe:
{:capacity=>0.0, :snapshot_id=>nil}
Are you sure 'name' should be in the opts? the values for
:capacity and :snapshot_id seem nondescript.
but I do see the GET on volumes list the name correctly.
and The xml and json both look correct when browsing to:
http://localhost:3001/cimi/volumes?format=xml
http://localhost:3001/cimi/volumes?format=json
The only incorrect behavior I observer is the "id" is displayed for the "name',
which seems wrong, when browsing to:
http://localhost:4001/cimi/volumes
What other indications do you have the the volume name is not set correctly?
> cimi: volume name is not set
> ----------------------------
>
> Key: DTACLOUD-390
> URL: https://issues.apache.org/jira/browse/DTACLOUD-390
> Project: DeltaCloud
> Issue Type: Bug
> Components: CIMI/Frontend
> Environment: any driver, reproducible with mock
> Reporter: Dies Koper
> Assignee: Joseph J. VLcek
>
> To reproduce, in mock driver, add debugging statement:
> def create_storage_volume(credentials, opts={})
> p opts # print passed-in options
> d:\>curl --user "mockuser:mockpassword"
> http://localhost:3001/cimi/volumes?format=xml -X POST -H "Content-Type:
> application/json" [email protected]
> with create-volume.json:
> { "resourceURI": "http://schemas.dmtf.org/cimi/1/VolumeCreate";, "name":
> "myVolume1", "description": "My first new volume", "volumeTemplate": {
> "volumeConfig": { "href": "http://example.com/vConfigs/small"; } } }
> server outputs:
> {:capacity=>0, :snapshot_id=>nil}
> Note no 'name'. Also note that doing a GET on volumes does list the name
> correctly, don't let it fool you.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
