[
https://issues.apache.org/jira/browse/DTACLOUD-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dies Koper closed DTACLOUD-536.
-------------------------------
I noticed David pushed a fix in commit 04006b7a03073f16804a1911b4bd34b5776ec4a8.
I confirmed in my repo, at commit 29b551fa1761b047767fb45db6b1ae74a6f8f858,
that the disks are now retrieved correctly:
d:\projects>curl --user mockuser:mockpassword
http://localhost:3001/cimi/machines/inst0/disks?format=xml
<Collection href="http://localhost:3001/cimi/machines/inst0/disks";
xmlns="http://schemas.dmtf.org/cimi/1";
resourceURI="http://schemas.dmtf.org/cimi/1/DiskCollec
tion">
<id>http://localhost:3001/cimi/machines/inst0/disks</id>
<count>1</count>
<Disk>
<id>http://localhost:3001/cimi/machines/inst0/disks/inst0_disk_0</id>
<name>inst0_disk_0</name>
<description>Disk for Machine inst0</description>
<created>2013-04-22T13:50:10+10:00</created>
<capacity>0</capacity>
</Disk>
</Collection>
> cimi: machine disks GET returns error
> -------------------------------------
>
> Key: DTACLOUD-536
> URL: https://issues.apache.org/jira/browse/DTACLOUD-536
> Project: DeltaCloud
> Issue Type: Bug
> Components: CIMI/Frontend
> Environment: reproduced on mock, fgcp, with current master (commit
> 0c7f632f17db7947662fc82eac798cb000ed1004)
> Reporter: Dies Koper
> Assignee: David Lutterkort
>
> Can't retrieve listing of machine's disks:
> curl --user mockuser:mockpassword
> http://localhost:3001/cimi/machines/inst0/disks?format=xml
> (json gives same error)
> E, [2013-04-06T22:00:03.156866 #9264] ERROR -- 500: [NoMethodError] undefined
> method `schema' for CIMI::Service::Disk:Class
> d:/sources/OSS/cloud/deltacloud/server/lib/cimi/models/collection.rb:34:in
> `generate'
> d:/sources/OSS/cloud/deltacloud/server/lib/cimi/service/disk.rb:66:in
> `collection_for_instance'
> d:/sources/OSS/cloud/deltacloud/server/lib/cimi/collections/machines.rb:72:in
> `block (3 levels) in <class:Machines>'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-rabbit-1.1.6/lib/sinatra/rabbit/base.rb:400:in
> `instance_eval'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-rabbit-1.1.6/lib/sinatra/rabbit/base.rb:400:in
> `block in control'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:1293:in
> `call'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:1293:in
> `block in compile!'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:860:in
> `[]'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:860:in
> `block (3 levels) in route!'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:876:in
> `route_eval'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:860:in
> `block (2 levels) in route!'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:897:in
> `block in process_route'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:895:in
> `catch'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:895:in
> `process_route'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:859:in
> `block in route!'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:858:in
> `each'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:858:in
> `route!'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:963:in
> `block in dispatch!'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:946:in
> `block in invoke'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:946:in
> `catch'
> D:/Programs/Ruby193/lib/ruby/gems/1.9.1/gems/sinatra-1.3.5/lib/sinatra/base.rb:946:in
> `invoke'
> 127.0.0.1 - - [06/Apr/2013 22:00:03] "GET
> /cimi/machines/inst0/disks?format=xml HTTP/1.1" 500 51652 0.0190
--
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
