Bug 1802223 - "Storage consumption" - incorrect recalculate
Summary: "Storage consumption" - incorrect recalculate
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.8.0
Hardware: x86_64
OS: Linux
unspecified
unspecified with 2 votes
Target Milestone: ovirt-4.4.0
: 4.4.0
Assignee: shani
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-12 16:11 UTC by s.fedorenko
Modified: 2020-08-05 06:09 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.4.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-05 06:09:55 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)
Archive with screenshots mentioned in Description (456.09 KB, application/zip)
2020-02-12 16:11 UTC, s.fedorenko
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 108573 0 master MERGED core: set value for setStorageSizeGBUsage 2020-11-16 17:21:12 UTC

Description s.fedorenko 2020-02-12 16:11:41 UTC
Created attachment 1662707 [details]
Archive with screenshots mentioned in Description

Description of problem:
After create first VPS disk with allowed size (in our example – 40GB), parameter “Storage consumption” changed on value of existing disk (pic 1 – pic 2). However, this parameter ignores next disks creation and as result – we can create additional disk with capacity much bigger that configured quota limit. “Storage consumption” parameter still on 60% even when total size of created disks is 492GB out of 80GB (~600%) (pic. 3)
Quota policy can be updated in manual mode. It seems that trigger works on Quota parameter change event. We started to “Edit” quota parameters and immediately press “OK” without any changes. After this operation parameter “Storage consumption” recalculates and quota limit marked as 100% (pic 4)

Description of testing procedure
1. Datacenter policy configured in “enforced” mode (pic.5)
2. Disk quota set to 80GB (pic.6).

Version-Release number of selected component (if applicable):
oVirt version 4.3.8


How reproducible:
every time

Steps to Reproduce:
1. configure disk quota
2. create VPS with disk size < disk_quota
3. add additional disks to have total disk storage > disk_quota
4. check that "Storage consumption" parameter did not recalculate after additional disks attach

Actual results:
System did not recalculate disk usage. As result - user can add more disks, that configured in his limits

Expected results:
Disk quota limits user to prevent create too much disks

Additional info:
1. Admin portal was launched in Google Chrome x86_64 version 80.0.3987.87
2. VM portal was launched in Mozilla Firefox x86_64 version 72.0.2
3. We tried to update browser page, but it did not made any changes.
4. We tried to use both dedicated and thin disks mode. Behavior still the same on both mode.

Comment 1 RHEL Program Management 2020-02-17 15:29:02 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.

Comment 2 s.fedorenko 2020-02-23 16:44:23 UTC
Hey, guys.

It seems that last message indicate some incorrect value in one field of ticket.
It is my first ticket in RH bugzilla, so, please, give me some advice if any actions from my side needed here.

Thanks.

Comment 3 RHEL Program Management 2020-04-16 10:31:13 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.

Comment 6 Avihai 2020-06-01 10:45:15 UTC
Verified on ovirt-engine 4.4.1.1-0.5.el8ev.

"Storage consumption" parameter did recalculate after additional disks attached and after reaching quota it was not allowed to add more disks to cross the set quota.

Comment 7 Sandro Bonazzola 2020-08-05 06:09:55 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.