[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601855#comment-15601855
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9560:
--------------------------------------------

GitHub user yvsubhash opened a pull request:

    https://github.com/apache/cloudstack/pull/1726

    CLOUDSTACK-9560 Root volume of deleted VM left unremoved

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yvsubhash/cloudstack CLOUDSTACK-9560

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1726.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1726
    
----
commit a4e8cc20db18e04ec8cce4a90676b5ef632debe9
Author: subhash yedugundla <venkatasubhashnaidu.yedugun...@citrix.com>
Date:   2016-05-31T11:45:04Z

    CLOUDSTACK-9560 Root volume of deleted VM left unremoved

----


> 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)

Reply via email to