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

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

DaanHoogland commented on issue #2090: CLOUDSTACK-8415 [VMware] SSVM shutdown 
during snapshot operation results in disks to be left behind
URL: https://github.com/apache/cloudstack/pull/2090#issuecomment-385161954
 
 
   @sureshanaparti sorry for totally missing this. Yes this looks like what I 
asked for. please rebase as @rhtyd asked so we can test and merge.

----------------------------------------------------------------
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


> [VMware] SSVM shutdown during snapshot operation results in disks to be left 
> behind 
> ------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8415
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8415
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Likitha Shetty
>            Assignee: Suresh Kumar Anaparti
>            Priority: Major
>             Fix For: Future
>
>
> Partial disks are residue of a failed snapshot operation caused by SSVM 
> reboot/shutdown. The disks do not get cleaned up on secondary storage and 
> need to be cleaned up manually to release storage.
> +Steps to reproduce+
> 1. Initiate a volume snapshot operation.
> 2. Destroy SSVM while the operation is in progress.
> 3. Check the snapshot folder in secondary storage - Files including disks are 
> present in the folder and are never cleaned up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to