[jira] [Updated] (DTACLOUD-390) cimi: volume name is not set
[
https://issues.apache.org/jira/browse/DTACLOUD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph J. VLcek updated DTACLOUD-390:
-
Attachment: 0001-DTACLOUD-390-Add-name-when-creating-volume.patch
I still need to better test this patch but I think this is the correct fix.
> 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
> Attachments: 0001-DTACLOUD-390-Add-name-when-creating-volume.patch
>
>
> 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": "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
[jira] [Updated] (DTACLOUD-390) cimi: volume name is not set
[
https://issues.apache.org/jira/browse/DTACLOUD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph J. VLcek updated DTACLOUD-390:
-
Attachment: 0001-DTACLOUD-390-Add-name-when-creating-volume.patch
I still need to better test this patch but I think this is the correct fix.
> 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
> Attachments: 0001-DTACLOUD-390-Add-name-when-creating-volume.patch
>
>
> 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": "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
[jira] [Updated] (DTACLOUD-390) cimi: volume name is not set
[
https://issues.apache.org/jira/browse/DTACLOUD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph J. VLcek updated DTACLOUD-390:
-
Attachment: 0001-DTACLOUD-390-Add-name-when-creating-volume.patch
I still need to better test this patch but I think this is the correct fix.
> 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
> Attachments: 0001-DTACLOUD-390-Add-name-when-creating-volume.patch
>
>
> 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": "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
[jira] [Commented] (DTACLOUD-400) "POST /cimi/volumes" returns 412 Precondition Failed for server pointing at RHEVM provider
[ https://issues.apache.org/jira/browse/DTACLOUD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534289#comment-13534289 ] Joseph J. VLcek commented on DTACLOUD-400: -- After applying this patch I do not observer any change in behavior. deltacloudd still returns a 412. X.X.X.X - - [17/Dec/2012 15:40:05] "POST /cimi/volumes?format=xml HTTP/1.1" 412 60 0.1698 Am I missing something or does the patch perhaps not fix this? > "POST /cimi/volumes" returns 412 Precondition Failed for server pointing at > RHEVM provider > -- > > Key: DTACLOUD-400 > URL: https://issues.apache.org/jira/browse/DTACLOUD-400 > Project: DeltaCloud > Issue Type: Bug > Components: CIMI/Frontend > Environment: Deltacloud commit version: > 15c1e8b702460b43fc445cbbc13657d9affd2977 > RHEVM 3.0 >Reporter: Ronelle Landy >Assignee: Marios Andreou > Attachments: > 0001-CIMI-dont-expose-add-URI-for-collection-if-not-suppo.patch, > 0002-CIMI-tests-skip-if-capability-supported-DTACLOUD-400.patch > > > Found while running cimiplan tests - part4_test.rb - testing Deltacloud > server with cimi frontend - pointing at RHEVM provider: > Executing the following lines in the test code: > * > volume = post(volume_add_uri, > "" + > "cimi_volume_for_attach_new" + > "volume for attach testing" + > "" + > "" + > "" + > "" + > "", > :accept => :json, :content_type => :xml) > ** > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in > `return!': 412 Precondition Failed (RestClient::PreconditionFailed) > from > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:230:in > `process_result' > from > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in > `transmit' > from /usr/lib/ruby/1.8/net/http.rb:543:in `start' > from > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in > `transmit' > from > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in > `execute' > from > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in > `execute' > from > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient.rb:72:in `post' > from ./test_helper.rb:153:in `post' -- 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
