deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-552) cimi: 202 Accepted response returns error template with backtrace
Date Wed, 24 Apr 2013 22:53:16 GMT


Dies Koper commented on DTACLOUD-552:

Here's a bit more of the backtrace (it's several pages long):

`block in delete_firewall'
    /home/dc/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:220:in `call'
    /home/dc/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:220:in `safely'
    /home/dc/deltacloud/server/lib/deltacloud/drivers/fgcp/fgcp_driver.rb:1119:in `delete_firewall'
    /home/dc/deltacloud/server/lib/cimi/service/system.rb:43:in `delete!'
    /home/dc/deltacloud/server/lib/cimi/helpers/cimi_rabbit_helper.rb:9:in `block (2 levels)
in generate_delete_operation'
> cimi: 202 Accepted response returns error template with backtrace
> -----------------------------------------------------------------
>                 Key: DTACLOUD-552
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: CIMI/Frontend, Server
>            Reporter: Dies Koper
>            Priority: Minor
> FGCP returns a 202 Accepted to a delete request for a system as it requires to make two
subsequent (time taking) calls to the backend: stopping the embedded FW and then destroying
the system. The 202 contains a message saying that the FW/system "will be deleted once it
has stopped".
> Problem is how the message is wrapped:
> <error status='202' url='/cimi/systems/UZXC0GRT-3KIYQVLJC'>
>   <backend driver='fgcp' provider='default'></backend>
>   <code>202</code>
>   <message><![CDATA[Firewall will be deleted once it has stopped]]></message>
>   <backtrace>
>     <![CDATA[/home/dc/deltacloud/server/lib/deltacloud/drivers/fgcp/fgcp_driver.rb:1145:in
`block in delete_firewall'
> 2xx responses shouldn't be marked as "error" and don't need a backtrace.

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:

View raw message