Github user adwaitpatankar commented on the issue:
https://github.com/apache/cloudstack/pull/1857
@ustcweizhou, the issue is that the resource count at domain level are not
getting updated implicitly after expunge VM call. If the user tries to add a
new instance, and if the primary storage resource count is not up to date, then
it results in a false alarm (exception) and not allowing the user to create a
guest instance even though the requested storage space is withing the limits of
the domain quota.
When we do not pass accountID (as per the fix), the resource counts would
be getting calculated on expungeVM event at Domain level which is the
expectation as per the ticket. Also when the resource calculation is done at
Domain level, all resource counts for all accounts within that domain are
recalculated as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
