You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/15 09:20:58 UTC
[jira] [Commented] (CLOUDSTACK-9560) Root volume of deleted VM left
unremoved
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750876#comment-15750876 ]
ASF GitHub Bot commented on CLOUDSTACK-9560:
--------------------------------------------
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/1726
@ustcweizhou Volume snapshots would be left over even in case of normal vm destroy and that is expected. They can be used if there is a need to restore the volume at a later point in time. The snapshots are visible under storage->snapshots. So i dont see a need to clean up those snapshots
> Root volume of deleted VM left unremoved
> ----------------------------------------
>
> Key: CLOUDSTACK-9560
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9560
> 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: XenServer
> Reporter: subhash yedugundla
> Fix For: 4.8.1
>
>
> In the following scenario root volume gets unremoved
> Steps to reproduce the issue
> 1. Create a VM.
> 2. Stop this VM.
> 3. On the page of the volume of the VM, click 'Download Volume' icon.
> 4. Wait for the popup screen to display and cancel out with/without clicking the download link.
> 5. Destroy the VM
> Even after the corresponding VM is deleted,expunged, the root-volume is left in 'Expunging' state unremoved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)