[
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315755#comment-16315755
]
ASF GitHub Bot commented on CLOUDSTACK-10188:
---------------------------------------------
bwsw commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting for
primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-355895431
@rhtyd Do we have a chance including it to 4.11 yet? I overviewed Travis
logs and only one test fails which seems to be a timeout reason, not a real
failure. We already resolved conflicts twice against moving master. I don't
even imaging how much we will be asked to do so if waiting 4.12))
And I suppose it's a bug which is vital for users who use domains, because
It blocks creating new VMs.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Resource Accounting for primary storage is Broken
> -------------------------------------------------
>
> Key: CLOUDSTACK-10188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
> Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space
> resource counter is not updated for domain. This leads to the situation when
> domain resource statistics for primary storage is overfilled (statistics only
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround
> but not fixes the problem truly because when accounts inside domains use
> primary_storage allocation/deallocation intensively it leads to service block
> of operation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
