[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575495#comment-16575495
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9572:
--------------------------------------------

mike-tutkowski edited a comment on issue #1740: CLOUDSTACK-9572 Snapshot on 
primary storage not cleaned up after Stor…
URL: https://github.com/apache/cloudstack/pull/1740#issuecomment-411917522
 
 
   The code to retrieve only primary-storage snapshots is OK. The problem is 
when the snapshot is given to the Snapshot Service 
(snapshotSrv.deleteSnapshot(info);). At some point, not only does the snapshot 
on the primary storage get deleted, but so does the snapshot on secondary 
storage.
   
   When I comment out the code in snapshotMgr.cleanupSnapshotsByVolume, 
everything works the way it used to (meaning the snapshot on the original 
primary storage is stranded, but the volume is still associated with the 
correct snapshot on secondary storage).

----------------------------------------------------------------
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:
us...@infra.apache.org


> 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
(v7.6.3#76005)

Reply via email to