You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Jozef Zigmund (JIRA)" <ji...@apache.org> on 2012/06/11 17:44:42 UTC

[jira] [Created] (DTACLOUD-229) DC returns 500 (unhandled exception) when EC2 instance is terminated

Jozef Zigmund created DTACLOUD-229:
--------------------------------------

             Summary: DC returns 500 (unhandled exception) when EC2 instance is terminated
                 Key: DTACLOUD-229
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-229
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server
            Reporter: Jozef Zigmund
            Priority: Minor


When user requests DC for state of non EBS instance, that was terminated, he gets 500 [unhandled exception]. This's happened when non EBS was removed(terminated and after few mins removed) from EC2

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

        

[jira] [Commented] (DTACLOUD-229) DC returns 500 (unhandled exception) when EC2 instance is terminated

Posted by "Michal Fojtik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DTACLOUD-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294408#comment-13294408 ] 

Michal Fojtik commented on DTACLOUD-229:
----------------------------------------

Can you please attach a backtrace from /var/log/deltacloud/* ? I'm not able to reproduce this issue. I got instance in STOPPED state and the XML provided is OK. No 500 so far.
                
> DC returns 500 (unhandled exception) when EC2 instance is terminated
> --------------------------------------------------------------------
>
>                 Key: DTACLOUD-229
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-229
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Jozef Zigmund
>            Priority: Minor
>
> When user requests DC for state of non EBS instance, that was terminated, he gets 500 [unhandled exception]. This's happened when non EBS was removed(terminated and after few mins removed) from EC2.
> It could response 404.

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

        

[jira] [Updated] (DTACLOUD-229) DC returns 500 (unhandled exception) when EC2 instance is terminated

Posted by "Jozef Zigmund (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DTACLOUD-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jozef Zigmund updated DTACLOUD-229:
-----------------------------------

    Description: 
When user requests DC for state of non EBS instance, that was terminated, he gets 500 [unhandled exception]. This's happened when non EBS was removed(terminated and after few mins removed) from EC2.
It could response 404.

  was:When user requests DC for state of non EBS instance, that was terminated, he gets 500 [unhandled exception]. This's happened when non EBS was removed(terminated and after few mins removed) from EC2

    
> DC returns 500 (unhandled exception) when EC2 instance is terminated
> --------------------------------------------------------------------
>
>                 Key: DTACLOUD-229
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-229
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Jozef Zigmund
>            Priority: Minor
>
> When user requests DC for state of non EBS instance, that was terminated, he gets 500 [unhandled exception]. This's happened when non EBS was removed(terminated and after few mins removed) from EC2.
> It could response 404.

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