You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjay Tripathi (JIRA)" <ji...@apache.org> on 2013/07/15 11:18:49 UTC

[jira] [Commented] (CLOUDSTACK-3496) [Regression]Primary Storage resource usage is not getting updated if detached volume is deleted

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

Sanjay Tripathi commented on CLOUDSTACK-3496:
---------------------------------------------

Fix is available for review at: https://reviews.apache.org/r/12544/
                
> [Regression]Primary Storage resource usage is not getting updated if detached volume is deleted  
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3496
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3496
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Assignee: Sanjay Tripathi
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: apilog.log
>
>
> Setup :  Advanced Zone with Xen 6.2
> Steps: 
> 1. Create user  account and deploy VM -  It has ROOT disk of 20 GB .  Now primary storage resource usage is 20 GB
>  
> 2. Add a DATA volume with small offering (5GB) ,  Now primary storage resource usage is 25 GB
> 3. Attach this volume to the instance. 
> 4. Detach the volume 
> 5. Delete the volume which is deleted . There is no change in primary storage resource usage even after deleting the volume of 5 GB.  It is still 25 GB. 
> Observation:
> Primary Storage resource usage is not getting updated if detached volume is deleted  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira