[
https://issues.apache.org/jira/browse/CLOUDSTACK-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753762#comment-15753762
]
ASF GitHub Bot commented on CLOUDSTACK-9560:
--------------------------------------------
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1726
@yvsubhash I did not mean we need clean up the snapshots.
in my understanding, if the volume has snapshots left, it is Expunged, but
not marked as Removed
your change just delete one snapshot and then mark the volume as Removed,
however, there might be other snapshots left (in this case, we should not mark
the volume as Removed)
> 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)
