[jira] [Resolved] (CLOUDSTACK-8889) Primary Storage count for an account does not decrease when a Data Disk is deleted belonging to the account unless the VM to which volume belonged is destroyed

["Rafael Weingärtner (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael Weingärtner resolved CLOUDSTACK-8889.
--------------------------------------------
    Resolution: Fixed

> Primary Storage count for an account does not decrease when a Data Disk is deleted belonging to the account unless the VM to which volume belonged is destroyed
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8889
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8889
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.2, 4.6.0
>            Reporter: Rajani Karuturi
>            Assignee: Rajani Karuturi
>            Priority: Major
>
> Steps to reproduce:
> 1. Create an account, deploy a VM in it
> 2. Create a data disk and attach to VM
> 3. Check the primary storage count for the account with listAccounts API
> 4. Delete the Data disk
> 5. Check the primary storage count for the account with listAccounts API - It is the same as before deleting the data disk
> It should decrease when data disk is deleted.
> Now delete the VM. You can see the primary storage count is decreased by (root volume size + data disk size)
> Primary Storage Limits test cases are failing due to this.
> testReport/junit/integration.component.test_ps_limits/TestVolumeLimits/test_create_multiple_volumes_1_root_domain_admin/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)