[ 
https://issues.apache.org/jira/browse/DTACLOUD-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ronelle Landy closed DTACLOUD-52.
---------------------------------

    Resolution: Fixed

Looks to be working now (see copied API output below). Note that there is no 
'medium' hardware profile in RHEVM - using SERVER profile

[rlandy@localhost ~]$ curl -X POST -F 
"image_id=ccf52584-4ec8-49cb-9f1b-9d214abfff5f" -F 
"name=differentRealmSpecifiedSERVER" -F 
"realm_id=bdce3f96-4070-11e1-9f90-5cf3fc1c861c" -F 'hwp_id=SERVER' --user 
'username:password' "http://server:3001/api/instances?format=xml";

<?xml version='1.0' encoding='utf-8' ?>
<instance 
href='http://server:3001/api/instances/50210ea1-2e60-4f6c-a2de-bab0ccdeea0d' 
id='50210ea1-2e60-4f6c-a2de-bab0ccdeea0d'>
  <name>differentRealmSpecifiedSERVER</name>
  <owner_id>xxx</owner_id>
  <image 
href='http://server:3001/api/images/ccf52584-4ec8-49cb-9f1b-9d214abfff5f' 
id='ccf52584-4ec8-49cb-9f1b-9d214abfff5f'></image>
  <realm 
href='http://server:3001/api/realms/bdce3f96-4070-11e1-9f90-5cf3fc1c861c' 
id='bdce3f96-4070-11e1-9f90-5cf3fc1c861c'></realm>
  <state>PENDING</state>
  <hardware_profile href='http://server:3001/api/hardware_profiles/SERVER' 
id='SERVER'>
    <property kind='fixed' name='memory' unit='MB' value='512'></property>
    <property kind='fixed' name='storage' unit='GB' value='1'></property>
    <property kind='fixed' name='cpu' unit='count' value='1'></property>
  </hardware_profile>
  <actions>
    <link 
href='http://server:3001/api/images;instance_id=50210ea1-2e60-4f6c-a2de-bab0ccdeea0d'
 method='post' rel='create_image' />
  </actions>
  <launch_time>2012-01-18T11:14:00.456-05:00</launch_time>
  <public_addresses><address port='5890' 
type='vnc'>127.0.0.1</address></public_addresses>
  <private_addresses></private_addresses>
</instance>

                
> using the RHEV driver, launching a new instance fails
> -----------------------------------------------------
>
>                 Key: DTACLOUD-52
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-52
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Client (Ruby)
>         Environment: http://10.65.193.195:3001/api/instances
>            Reporter: Shveta Sachdeva
>            Assignee: David Lutterkort
>              Labels: rhev
>
> recreate:
> 1. login, -> instances
> 2. choose a template
> 3. launch an instance.. used a "medium" hardware profile
> Deltacloud::ExceptionHandler::BackendError: ERROR: Operation start failed
> ././lib/deltacloud/drivers/rhevm/rhevm_driver.rb:142:in `start_instance'
>               ././lib/deltacloud/base_driver/exceptions.rb:111:in `call'
>               ././lib/deltacloud/base_driver/exceptions.rb:111:in `safely'
>               ././lib/deltacloud/drivers/rhevm/rhevm_driver.rb:141:in 
> `start_instance'
>               ././lib/deltacloud/helpers/application_helper.rb:127:in `send'
>               ././lib/deltacloud/helpers/application_helper.rb:127:in 
> `instance_action'
>               ././server.rb:423
>               ././lib/sinatra/rabbit.rb:113:in `instance_eval'
>               ././lib/sinatra/rabbit.rb:113:in `POST /api/instances/:id/start'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:863:in `call'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:863:in `route'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:521:in 
> `instance_eval'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:521:in 
> `route_eval'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:500:in `route!'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:497:in `catch'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:497:in `route!'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:476:in `each'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:476:in `route!'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:601:in `dispatch!'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in 
> `instance_eval'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `catch'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:399:in `call'
>               ././lib/sinatra/rack_driver_select.rb:45:in `call'
>               ././lib/sinatra/rack_matrix_params.rb:85:in `call'
>               ././lib/sinatra/rack_runtime.rb:36:in `call'
>               ././lib/sinatra/rack_etag.rb:42:in `call'
>               
> /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/context.rb:22:in
>  `call'
>               
> /usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call'
>               
> /usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/commonlogger.rb:18:in `call'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:1005:in 
> `synchronize'
>               
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'
>               /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/stats.rb:24:in 
> `call'
>               /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/stats.rb:33:in 
> `log'
>               /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/stats.rb:24:in 
> `call'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:76:in 
> `pre_process'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:74:in `catch'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:74:in 
> `pre_process'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in 
> `call'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in 
> `spawn_threadpool'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in 
> `initialize'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in 
> `new'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in 
> `spawn_threadpool'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in 
> `defer'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:54:in `process'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/connection.rb:42:in 
> `receive_data'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in 
> `run_machine'
>               
> /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in 
> `run'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/backends/base.rb:57:in `start'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/server.rb:156:in `start'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/controllers/controller.rb:80:in
>  `start'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/runner.rb:177:in `send'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/runner.rb:177:in `run_command'
>               
> /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/lib/thin/runner.rb:143:in `run!'
>               /usr/lib/ruby/gems/1.8/gems/thin-1.2.5/bin/thin:6
>               /usr/bin/thin:19:in `load'
>               /usr/bin/thin:19

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to