[
https://issues.apache.org/jira/browse/CLOUDSTACK-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594838#comment-15594838
]
ASF GitHub Bot commented on CLOUDSTACK-9558:
--------------------------------------------
GitHub user yvsubhash opened a pull request:
https://github.com/apache/cloudstack/pull/1722
CLOUDSTACK-9558 Cleanup the snapshots on the primary storage of Xense…
Cleanup the snapshots on the primary storage of Xenserver after VM/Volume
is expunged
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yvsubhash/cloudstack CLOUDSTACK-9558
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1722.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1722
----
commit 0ff5a5329ec047fe4872347a26236da75ce5eef7
Author: subhash_y <subhash yedugundla>
Date: 2016-08-29T05:15:03Z
CLOUDSTACK-9558 Cleanup the snapshots on the primary storage of Xenserver
after VM/Volume is expunged
----
> 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)
