You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/07/03 16:50:19 UTC
[jira] [Updated] (CLOUDSTACK-3350) Snapshots not deleted from swift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasanna Santhanam updated CLOUDSTACK-3350:
-------------------------------------------
Priority: Major (was: Minor)
> Snapshots not deleted from swift
> --------------------------------
>
> Key: CLOUDSTACK-3350
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3350
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Snapshot
> Affects Versions: 4.0.1
> Environment: Xenserver 6.0
> Reporter: Magnus Bengtsson
>
> When using swift for secondary strorage, deletetion of snapshots fails on swift.
> The storage VM tries to delete V-[volumeid], but snapshots are stored as S-[volumeid] on Swift.
> Execerpt from swift proxy log, when creating and then deleting a snapshot in CS:
> Jul 3 16:29:53 rbc-proxy01 proxy-server XXX 10.101.5.5 03/Jul/2013/14/29/53 PUT /v1/CSAUTH_2f2a7eb3-9514-4319-a047-f4bac0d63a62/S-44/48482acb-2eeb-442a-aa90-04aa9c45d1c6.vhd HTTP/1.0 201 - - 2008834560 - - tx1082fb1a95d34fc3ae10e986e0924f47 - 53.8997 -
> Jul 3 16:30:47 rbc-proxy01 proxy-server XXX 10.101.5.5 03/Jul/2013/14/30/47 GET /auth/v1.0 HTTP/1.0 200 - - - - - - - 0.0006 -
> Jul 3 16:30:47 rbc-proxy01 proxy-server XXX 10.101.5.5 03/Jul/2013/14/30/47 HEAD /v1/CSAUTH_2f2a7eb3-9514-4319-a047-f4bac0d63a62/V-44/48482acb-2eeb-442a-aa90-04aa9c45d1c6.vhd HTTP/1.0 404 - - - - - - 0.0231 -
> Jul 3 16:30:47 rbc-proxy01 proxy-server XXX 10.101.5.5 03/Jul/2013/14/30/47 DELETE /v1/CSAUTH_2f2a7eb3-9514-4319-a047-f4bac0d63a62/V-44/48482acb-2eeb-442a-aa90-04aa9c45d1c6.vhd HTTP/1.0 404 - - - 70 - - 0.0010 -
--
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