deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph J. VLcek (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-390) cimi: volume name is not set
Date Wed, 05 Dec 2012 22:31:58 GMT


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:

The only incorrect behavior I observer is the "id" is displayed for the "name', which seems
wrong, when browsing to:

What other indications do you have the the volume name is not set correctly?

> cimi: volume name is not set
> ----------------------------
>                 Key: DTACLOUD-390
>                 URL:
>             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"  -d@create-volume.json
> with create-volume.json:
> { "resourceURI": "", "name": "myVolume1",
"description": "My first new volume", "volumeTemplate": { "volumeConfig": { "href": ""
} } }
> 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:

View raw message