Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1530249

Summary:	Default quota must be updated - still contains 0% (invalid value)
Product:	[oVirt] ovirt-engine	Reporter:	Polina <pagranat>
Component:	Frontend.WebAdmin	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	akrejcir, bugs, ljelinko, lsvaty, rbarry, tjelinek
Target Milestone:	ovirt-4.4.0	Keywords:	EasyFix
Target Release:	---	Flags:	rule-engine: ovirt-4.4+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.0 gitb5b5c99ca2f	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:04:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.