ASF GitHub Bot commented on CLOUDSTACK-9572:

mike-tutkowski commented on issue #1740: CLOUDSTACK-9572 Snapshot on primary 
storage not cleaned up after Stor…
URL: https://github.com/apache/cloudstack/pull/1740#issuecomment-412284480
   I am not in front of the code right now, but I think the root problem is 
that we do not currently have a mechanism which allows us to delete the (delta) 
snapshot on primary storage without removing what it corresponds to on 
secondary storage.
   On Aug 11, 2018, at 9:49 AM, Rafael Weingärtner 
<notificati...@github.com<mailto:notificati...@github.com>> wrote:
   Thanks for your details @mike-tutkowski<https://github.com/mike-tutkowski>. 
Can you help me understand where the problem is?
   Is the problem in snapshotSrv.deleteSnapshot(info) that is deleting the 
snapshot from the secondary storage as well, and not only in the primary 
storage? Or is the code that the PR is introducing that is using the method 
snapshotSrv.deleteSnapshot in an incorrect manner?
   You are receiving this because you were mentioned.
   Reply to this email directly, view it on 
or mute the 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Snapshot on primary storage not cleaned up after Storage migration
> ------------------------------------------------------------------
>                 Key: CLOUDSTACK-9572
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9572
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Storage Controller
>    Affects Versions: 4.8.0
>         Environment: Xen Server
>            Reporter: subhash yedugundla
>            Priority: Major
>             Fix For: 4.8.1
> Issue Description
> ===============
> 1. Create an instance on the local storage on any host
> 2. Create a scheduled snapshot of the volume:
> 3. Wait until ACS created the snapshot. ACS is creating a snapshot on local 
> storage and is transferring this snapshot to secondary storage. But the 
> latest snapshot on local storage will stay there. This is as expected.
> 4. Migrate the instance to another XenServer host with ACS UI and Storage 
> Live Migration
> 5. The Snapshot on the old host on local storage will not be cleaned up and 
> is staying on local storage. So local storage will fill up with unneeded 
> snapshots.

This message was sent by Atlassian JIRA

Reply via email to