Bug 1530249 - Default quota must be updated - still contains 0% (invalid value)
Summary: Default quota must be updated - still contains 0% (invalid value)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ovirt-4.4.0
: ---
Assignee: Lucia Jelinkova
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-02 11:19 UTC by Polina
Modified: 2020-05-20 20:04 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-4.4.0 gitb5b5c99ca2f
Clone Of:
Environment:
Last Closed: 2020-05-20 20:04:13 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100922 0 master MERGED core: added default values for quota 2020-03-25 11:55:57 UTC

Description Polina 2018-01-02 11:19:04 UTC
Description of problem:
Update of created quota to 0 is not impossible now , but the Default quota still contains 0

Version-Release number of selected component (if applicable):
rpm -qa | grep ovirt-engine-4

How reproducible:100%


Steps to Reproduce:
1.Open tab datacenters, choose DC and open Default quota

Actual results: the values for Threshholds are 0.


Expected results:
must be 80% 

Additional info:

Comment 1 Andrej Krejcir 2018-01-11 10:51:38 UTC
The default quota is created during engine-setup and it uses the default values for the threshold and grace. The values are part of the DB definition of the quota table.

I checked this on ovirt-engine master branch, version 4.2.2, and the default quota has the correct thresholds, 80%.

Comment 2 Andrej Krejcir 2018-02-09 09:49:26 UTC
Ignore my previous comment.
The 0 values are given to the Default quota in any newly created data center, which is a bug.

Comment 3 Michal Skrivanek 2020-03-10 12:25:50 UTC
change SLA team to virt, we're not tracking SLA separately anymore

Comment 4 Polina 2020-03-25 11:55:13 UTC
verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-23

Comment 5 Sandro Bonazzola 2020-05-20 20:04:13 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.