cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9560) Root volume of deleted VM left unremoved
Date Fri, 16 Dec 2016 10:40:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9560:

Github user yvsubhash commented on the issue:
    @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:
>             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
> 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

View raw message