+++ This bug was initially created as a clone of Bug #1814214 +++ Description of problem: Incorrect storage quota usage percentage level, eventually ending up to 0% or Unlimited. The problem is that it does not represents actual usage with certainty, but rather fluctuating between 0%, actual usage and Unlimited. With some of my data centers, I initially saw it working, then it moved to 0% or Unlimited and it stays like that. Is there a trigger that tells the engine you need to calculate, or if it can be configurable, I do not know, documentation is not very detailed on this part. Version-Release number of selected component (if applicable): ovirt-engine-4.3.8.2 ovirt-engine-4.3.5.4 How reproducible: 60% as I have multiple data centers with quotas Steps to Reproduce: 1. set to Enforced / create storage quota / add consumer(s) 2. assign this quota to all existing VMs and related images 3. if present, assing to templates as well Actual results: Storage Quota percentage shows 0% or Unlimited Expected results: Storage quota percentage reflecting actual usage Additional info: Check the screenshots attached. SanJose - storage quota percentage vs storage quota actual utilization Hilversum - same thing --- Additional comment from RHEL Program Management on 2020-03-17 12:34:12 UTC --- The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. --- Additional comment from Marko Vrgotic on 2020-03-24 08:24:23 UTC --- Hi RedHat, Not sure if the above was a question to me, but I am not reporting Documentation bug but actual software bug. If you need me to provide more data, logs, conf files, I have three platforms deployed, all having same issue. Marko Vrgotic --- Additional comment from Marko Vrgotic on 2020-04-06 07:20:40 UTC --- Dear RedHat and oVirt, Considering this COVID-19 situation, I hope you are all doing well and staying healthy. It has been more than two weeks since I reported this issue. So far I have not received a single update or request, and the issue is still registered as NEW. Considering this is one out of three issues regarding oVirt quotas, that I reported, in one day, not getting any update leads me to assumptions: - I am doing something fundamentally wrong with oVirt Quotas implementation - There is something fundamentally wrong with oVirt Quotas implementation, from the software side. - something else… In any case, I would highly appreciate it if you can find time to look into these issues so we can make progress. Once again, I am seeing this problem on all three deployed platforms, both in Staging and Production. Kindly awaiting your reply. Marko Vrgotic ActiveVideo --- Additional comment from Marko Vrgotic on 2020-07-14 14:51:05 UTC --- Dear all, Is this still targeted for 4.5? If any additional information is needed, just let me know. Kindly awaiting your reply. Marko