deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-236) RHEVM: Clicking on Destroy button on a stopped instance results in "OVIRT::OvirtException:Entity not found: id" exception
Date Mon, 01 Oct 2012 08:39:08 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466697#comment-13466697
] 

Michal Fojtik commented on DTACLOUD-236:
----------------------------------------

Hi Ronelle,

Unfortunately we can't add any delay there, because API is stateless, mean we're not storing
the state anywhere.
I think this might be a 'bug' of RHEV-M API or we're translating some state incorrectly. If
the transition between
'RUNNING' and 'STOPPED" is direct (so there is no 'middle-state') then definitely a RHEV-M
bug.
But if there is some state between those two, we should report that as a 'PENDING'. Going
to investigate
this today...
                
> RHEVM: Clicking on Destroy button on a stopped instance results in "OVIRT::OvirtException:Entity
not found: id" exception
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-236
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-236
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: Commit - 43af3a1e109cc608af654b0e016f35c741635d2a
> OS - Fedora 16, RHEL 6.2
> rbovirt (0.0.12)
>            Reporter: Ramesh A
>            Assignee: Michal Fojtik
>
> Clicking on Destroy button on a stopped instance results in "OVIRT::OvirtException:Entity
not found: id" exception in RHEVM step
> Reproduction Steps:
> ==============
> 1. Start an instance from an image
> 2. Click on the above instance and click on destroy button (as its in the stopped state)
> Expected Result:
> =============
> Should be able to destroy the instance
> Actual Result:
> ===========
> Throws "OVIRT::OvirtException:Entity not found: id" exception.  Refer the Screenshot
"RHEVM-Error.png" and Log Trace for further information
> Log Trace:
> =========
> 10.11.10.188 - - [13/Jun/2012 12:36:34] "GET /api/instances HTTP/1.1" 200 22416 11.4034
> 10.11.10.188 - - [13/Jun/2012 12:37:10] "GET /api/instances/e0bbe489-a844-488f-8c2a-fc9410b06e35
HTTP/1.1" 200 5179 11.5450
> 10.11.10.188 - - [13/Jun/2012 12:37:30] "DELETE /api/instances/e0bbe489-a844-488f-8c2a-fc9410b06e35
HTTP/1.1" 303 - 12.0775
> OVIRT::OvirtException:Entity not found: id
> /usr/lib/ruby/gems/1.8/gems/rbovirt-0.0.12/lib/rbovirt.rb:131:in `handle_fault'
> /usr/lib/ruby/gems/1.8/gems/rbovirt-0.0.12/lib/rbovirt.rb:69:in `http_get'
> /usr/lib/ruby/gems/1.8/gems/rbovirt-0.0.12/lib/client/vm_api.rb:22:in `vm_interfaces'
> /usr/lib/ruby/gems/1.8/gems/rbovirt-0.0.12/lib/ovirt/vm.rb:21:in `interfaces'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/rhevm/rhevm_driver.rb:243:in
`convert_instance'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/rhevm/rhevm_driver.rb:131:in
`instances'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/rhevm/rhevm_driver.rb:130:in
`each'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/rhevm/rhevm_driver.rb:130:in
`instances'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `call'
> /usr/share/deltacloud-core/lib/deltacloud/./drivers/exceptions.rb:173:in `safely'
> /usr/share/deltacloud-core/lib/deltacloud/./helpers/../drivers/rhevm/rhevm_driver.rb:124:in
`instances'
> 10.11.10.188 - - [13/Jun/2012 12:37:42] "GET /api/instances HTTP/1.1" 500 244589 11.0477
> 10.11.10.188 - - [13/Jun/2012 12:37:50] "GET /api/%5C%5C%5C%22%5C%22%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn
HTTP/1.1" 404 962 0.0534
> 10.11.10.188 - - [13/Jun/2012 12:37:53] "GET /api/%5C%5C%5C%22%5C%22%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn%5Cn
HTTP/1.1" 404 962 0.1398

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

Mime
View raw message