You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/10/21 23:46:17 UTC

[jira] [Updated] (CLOUDSTACK-4625) Snapshots and templates should be deleted from staging storage after create template from snapshot on S3.

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

Animesh Chaturvedi updated CLOUDSTACK-4625:
-------------------------------------------


ACS 4.3,0 feature freeze is Nov 8th. I will cut the 4.3 branch from master on that day. Please provide an update on your issue as a comment. 

> Snapshots and templates should be deleted from staging storage after create template from snapshot on S3.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4625
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4625
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller, Volumes
>    Affects Versions: 4.2.0
>         Environment: Latest build from ACS 4.2 branch
> Storage: S3 for image store, NFS for secondary staging and primary storage
>            Reporter: Sanjeev N
>            Assignee: Min Chen
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> storage artifacts like snapshots and templates are not getting deleted from staging storage when template was created from snapshot.
> Following actions take place when template is created from snapshot:
> 1.Snapshot gets downloaded from S3 to snapshots directory in NFS staging storage
> 2.Then it gets copied to template directory in NFS staging storage
> 3.Finally it is uploaded to S3
> After successful operation snapshot and template copied to staging storage (in step1 and step2) should be deleted.



--
This message was sent by Atlassian JIRA
(v6.1#6144)