Ronelle Landy created DTACLOUD-370:
--------------------------------------

             Summary: GET /cimi/resource_metadata (Vsphere provider) causes 
"ERROR -- 500: [TypeError] can't convert Time into String"
                 Key: DTACLOUD-370
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-370
             Project: DeltaCloud
          Issue Type: Bug
          Components: CIMI/Frontend
         Environment: Deltacloud git commit 
34b34f221c4f0b6a1b219dbfc6d4902b7ae9b8ff
Vsphere 5
CIMI
            Reporter: Ronelle Landy


Start a Deltacloud server with all three frontends:
>>  API_PROVIDER=<ip of provider install> ./bin/deltacloudd -i vsphere -f 
>> cimi,deltacloud,ec2 -r <hostname>

Using the CIMI frontend, get the CEP and query supported collections. GET'ting 
the resource_metadata collection errors out...

10.11.8.9 - - [13/Nov/2012 19:39:16] "GET /cimi/resource_metadata HTTP/1.1" 200 
808 0.0056
E, [2012-11-13T19:39:21.162483 #16390] ERROR -- 500: [TypeError] can't convert 
Time into String

/usr/share/ruby/time.rb:265:in `_parse'
/usr/share/ruby/time.rb:265:in `parse'
/home/dcloud/workspace/deltacloud/server/lib/cimi/models/machine.rb:128:in 
`from_instance'
/home/dcloud/workspace/deltacloud/server/lib/cimi/models/machine.rb:40:in 
`block in find'
/home/dcloud/workspace/deltacloud/server/lib/cimi/models/machine.rb:40:in `map'
/home/dcloud/workspace/deltacloud/server/lib/cimi/models/machine.rb:40:in `find'
/home/dcloud/workspace/deltacloud/server/lib/cimi/models/collection.rb:117:in 
`list'
/home/dcloud/workspace/deltacloud/server/lib/cimi/collections/machines.rb:27:in 
`block (3 levels) in <class:Machines>'
/usr/local/share/gems/gems/sinatra-rabbit-1.1.2/lib/sinatra/rabbit/base.rb:394:in
 `instance_eval'
/usr/local/share/gems/gems/sinatra-rabbit-1.1.2/lib/sinatra/rabbit/base.rb:394:in
 `block in control'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:1265:in `call'

This works for the mock driver.



--
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

Reply via email to