Ronelle Landy created DTACLOUD-401:
--------------------------------------
Summary: CIMI: "can't find image in given datacenter" - Deltacloud
server point at Vsphere provider
Key: DTACLOUD-401
URL: https://issues.apache.org/jira/browse/DTACLOUD-401
Project: DeltaCloud
Issue Type: Bug
Components: CIMI/Frontend
Environment: Deltacloud commit version:
15c1e8b702460b43fc445cbbc13657d9affd2977
Vsphere 5.x
Reporter: Ronelle Landy
The error below seems legitimate ... ie: that Deltacloud is just reporting the
backend error - except that the image referred to is definitely available in
the Vsphere provider. (It's the default image used most in testing - as is
returned by the GET request below:)
**********
curl -X GET --user 'un:pw'
http://qe-blade-13.idm.lab.bos.redhat.com:3001/cimi/machine_images?format=xml
<id>http://qe-blade-13.idm.lab.bos.redhat.com:3001/cimi/machine_images</id>
<count>20</count>
<MachineImage>
<id>http://qe-blade-13.idm.lab.bos.redhat.com:3001/cimi/machine_images/AutoImageImport-DoNotDelete</id>
<name>AutoImageImport-DoNotDelete</name>
<description>Other Linux (64-bit)</description>
<created>2012-12-13T17:53:40-05:00</created>
<state>AVAILABLE</state>
<type>IMAGE</type>
<imageLocation>vsphere://AutoImageImport-DoNotDelete</imageLocation>
</MachineImage>
**********
Do I *need* to specify the datastore? (There is only one in this case).
ERROR -- 500: [Deltacloud::Exceptions::BackendError] ERROR: Could not find the
image in given datacenter
/home/dcloud/workspace/deltacloud/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:218:in
`block in create_instance'
/home/dcloud/workspace/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:212:in
`call'
/home/dcloud/workspace/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:212:in
`safely'
/home/dcloud/workspace/deltacloud/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:213:in
`create_instance'
/home/dcloud/workspace/deltacloud/server/lib/cimi/models/machine.rb:91:in
`create_from_xml'
/home/dcloud/workspace/deltacloud/server/lib/cimi/collections/machines.rb:52:in
`block (3 levels) in <class:Machines>'
/usr/local/share/gems/gems/sinatra-rabbit-1.1.3/lib/sinatra/rabbit/base.rb:396:in
`instance_eval'
/usr/local/share/gems/gems/sinatra-rabbit-1.1.3/lib/sinatra/rabbit/base.rb:396:in
`block in control'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:1265:in `call'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:1265:in `block in
compile!'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:835:in `[]'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:835:in `block (3
levels) in route!'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:851:in `route_eval'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:835:in `block (2
levels) in route!'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:872:in `block in
process_route'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:870:in `catch'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:870:in
`process_route'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:834:in `block in
route!'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:833:in `each'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:833:in `route!'
/usr/local/share/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:936:in `dispatch!'
10.11.11.227 - - [13/Dec/2012 17:48:20] "POST /cimi/machines HTTP/1.1" 500 1930
0.7406
Any thoughts on what's amiss here?
--
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
