cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "subhash yedugundla (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9560) Root volume of deleted VM left unremoved
Date Mon, 24 Oct 2016 12:30:58 GMT


subhash yedugundla commented on CLOUDSTACK-9560:

When a download is attempted a symbolic link would be created in SSVM and mapping would be
placed in volume_store_ref table. The link would expire after the global setting 'extract.url.expiration.interval'
which defaults to 4 hours and the expired links are cleaned up after the extract.url.cleanup.interval
after expiry which defaults to 2 hours. The deletion of volume would be restricted if there
is an entry for the volume in volume_store_ref table. After the expiry, the cleanup thread
clears the entries in the volume_store_ref table, not the entries in the volumes table.  If
the vm destroy is attempted after cleanup is done from volume_store_ref table, then the volumes
would be cleanup. However, If the vm is destroyed before the expiry, then this issue occurs.
So adding volume cleanup during cleanup of expired entries.

> 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