cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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
Date Mon, 21 Sep 2015 10:52:04 GMT

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

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

GitHub user karuturi opened a pull request:

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

    CLOUDSTACK-8889: delete volume doesnt decrement primary store resource count

    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
    
    The resource counts are updated even before the disk is actually deleted
    resulting in the same value.
    Moved the resource counts updation to after the expunge operation as
    thats when the disk is actually deleted.
    
    Testing:
     Earlier, test_create_multiple_volumes in test/integration/component/test_ps_limits.py
failed  with error AssertionError: Resource count 37 should match with the expected resource
count 32
    
    Before
    
    Test create multiple volumes ... === TestName: test_create_multiple_volumes_1_root_domain_admin
| Status : FAILED ===
    FAIL
    Test create multiple volumes ... === TestName: test_create_multiple_volumes_2_child_domain_admin
| Status : FAILED ===
    FAIL
    
    After the Fix
    
    Test create multiple volumes ... === TestName: test_create_multiple_volumes_1_root_domain_admin
| Status : SUCCESS ===
    ok
    Test create multiple volumes ... === TestName: test_create_multiple_volumes_2_child_domain_admin
| Status : SUCCESS ===
    ok
    
    ----------------------------------------------------------------------
    Ran 2 tests in 334.823s
    
    OK

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

    $ git pull https://github.com/karuturi/cloudstack CLOUDSTACK-8889

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

    https://github.com/apache/cloudstack/pull/860.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 #860
    
----
commit 4e56dfbfbfa82802f71717b333728d8b03d7892a
Author: Rajani Karuturi <rajani.karuturi@citrix.com>
Date:   2015-09-21T10:41:15Z

    CLOUDSTACK-8889: delete volume doesnt decrement primary store resource count
    
    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
    
    The resource counts are updated even before the disk is actually deleted
    resulting in the same value.
    Moved the resource counts updation to after the expunge operation as
    thats when the disk is actually deleted.
    
    all the tests in test/integration/component/test_ps_limits.py now pass

----


> 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: Task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rajani Karuturi
>
> 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.
> http://ccp-tests.xenrt.xs.citrite.net/jenkins/job/Guadalupe-Regression-Multi/CLOUDSTACK_CONFIG=AdvXS/23/testReport/junit/integration.component.test_ps_limits/TestVolumeLimits/test_create_multiple_volumes_1_root_domain_admin/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message