[
https://issues.apache.org/jira/browse/CLOUDSTACK-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754079#comment-15754079
]
ASF GitHub Bot commented on CLOUDSTACK-9560:
--------------------------------------------
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/1726
@ustcweizhou As I understand, Volume goes to Expunged state when it is
removed from primary and gets removed when it is removed from secondary
storage. line 2211 to 2215 is to handle specific case where volume getting
removed from primary But not getting removed from secondary because of the
download link. So cleaning up the same after the downlink is expired
> 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)
