[jira] [Commented] (CLOUDSTACK-9558) Cleanup the snapshots on the primary storage of Xenserver after VM/Volume is expunged

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user yvsubhash commented on the issue:

    https://github.com/apache/cloudstack/pull/1722
  
    @koushik-das can you please review


> Cleanup the snapshots on the primary storage of Xenserver after VM/Volume is expunged
> -------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9558
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9558
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Volumes
>    Affects Versions: 4.8.0
>         Environment: Xen Server
>            Reporter: subhash yedugundla
>             Fix For: 4.8.1
>
>
> Steps to reproduce the issue
> ===========================
> i) Deploy a new VM in CCP on Xenserver
> ii) Create a snapshot for the volume created in step i) from CCP. This step will create a snapshot on the primary storage and keeps it on storage as we use it as reference for the incremental snapshots
> iii) Now destroy and expunge the VM created in step i)
> You will notice that the volume for the VM ( created in step i) is deleted from the primary storage. However the snapshot created on primary ( as part of step ii)) still exists on the primary and this needs to be deleted manually by the admin.
> Snapshot exists on the primary storage even after deleting the Volume.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)