[
https://issues.apache.org/jira/browse/CLOUDSTACK-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713538#comment-13713538
]
ASF subversion and git services commented on CLOUDSTACK-3492:
-------------------------------------------------------------
Commit 539eb38908ede53a36d4bb680b848caf9fe469c4 in branch refs/heads/master
from [~sanjay.tripathi]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=539eb38 ]
CLOUDSTACK-3492: [Regression]Update Resource Count for an account is updating
the primary storage incorretly.
The issue is that while calculating the used primary storage size, the
updateResourceCount
API is also calculating the disk size of virtual router VM, created for that
account and
because of this, the API is returning the incorrect result.
> [Regression]Update Resource Count for an account is updating the primary
> storage incorretly
> --------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3492
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3492
> 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, management-server.log
>
>
> Steps:
> 1. Deploy instance with user account1
> 2. Get the primary storage is usage using ListAccounts- It is 10 GB same as
> ROOT disk size of this instance
> 3. Now tried Update Resource Count for this account. With this when verified
> the usage using listAccounts it increased to 11 GB
> 4. Added one DATA disk of 5 GB . With which usage has become 16 GB
> 5. Then tried Update Resource Count for this account. With this when
> verified the usage using listAccounts it decreased to 11 GB
> Observation :
> Update Resource Count for an account is updating the primary storage
> incorrectly (Attached API log)
--
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
