[
https://issues.apache.org/jira/browse/DTACLOUD-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-400.
----------------------------------
Marking this issue as closed in Deltacloud commit version:
8af48384a168898de9a7e1b3be328f1fe4128b78. (with some caveats)
The test output part4_test.rb is included below ...
Run options: --seed 41866
# Running tests:
SSSSSSSSSSSSSS
Finished tests in 14.741971s, 0.9497 tests/s, 0.0000 assertions/s.
14 tests, 0 assertions, 0 failures, 0 errors, 14 skips
CLEANING UP... resources for deletion: {:machine_images=>[], :volumes=>[],
:machines=>[], :machine_templates=>[]}
CLEANUP attempt finished... resources looks like: {}
I definitely have some reservations about the naming of the method
'needs_capability' - which seems to be a name space clash with resource meta
data. Also, I have some suspicion that other providers will not respond as well
(all tests are skipped and some *could* actually be run) but will open separate
JIRAs if need be - as these patches are already in the code base.
> "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,
> "<VolumeCreate xmlns=\"#{CIMI::Test::CIMI_NAMESPACE}\">" +
> "<name>cimi_volume_for_attach_new</name>" +
> "<description>volume for attach testing</description>" +
> "<volumeTemplate>" +
> "<volumeConfig href=\"" + get_a(cep_json, "volumeConfig") + "\">" +
> "</volumeConfig>" +
> "</volumeTemplate>" +
> "</VolumeCreate>",
> :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
