[
https://issues.apache.org/jira/browse/CLOUDSTACK-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769797#comment-15769797
]
ASF GitHub Bot commented on CLOUDSTACK-8284:
--------------------------------------------
GitHub user adwaitpatankar opened a pull request:
https://github.com/apache/cloudstack/pull/1857
BUG-ID: CLOUDSTACK-8284
On expunge VM, initiate resource count update at domain
level. Setting accountId as null ensures resource count is done at domain
level and any hierarchies below.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-8284
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1857.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 #1857
----
commit 468ec40963189f1e68be46c4c0f2955eb3a520ab
Author: Adwait Patankar <adwait_patan...@accelerite.com>
Date: 2016-07-27T20:41:11Z
BUG-ID: CLOUDSTACK-8284
On expunge VM, initiate resource count update at domain
level. Setting accountId as null ensures resource count is done
at domain level and any hierarchies below.
----
> Primary_storage vlaue is not updating in resource_count table after VM
> deletion
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8284
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8284
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.4.2
> Reporter: Sonali Jadhav
> Assignee: adwait patankar
>
> I was doing some tests for checking resource limitation behavior on
> sub-domain, a/c and project.
> For account , I didn't set any limits. Instead I set limits on sub-domain.
> But this specific Primary storage limit(40GB) acted weird.
> At first in sub-domain, I created new instance (without project), and
> assigned 41 GB, and it successfully created VM. Then I deleted that VM with
> Expunge option enabled, and tried to create vm again with disk size 42, which
> failed with error "Maximum number of resources of type 'primary_storage' for
> domain id=3 has been exceeded"
> Then I gave disk size to 39GB, that also failed with same error. And now if I
> create any disk size its failing. There are no instances or volumes under
> that sub-domain.
> so which i checked resource_count table, "count" for Primary_storage was not
> set to zero.
> So then I logged into same domain from UI, and in "Domains" section clicked
> on "update resource count". After which in resource_count table
> "primary_storage" table value went back to zero.
> For Reference:
> http://comments.gmane.org/gmane.comp.apache.cloudstack.user/17008
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
