Bug 1533160

Summary:	Webadmin-manage domain window - it's possible to insert a number bigger than storage domain size
Product:	[oVirt] ovirt-engine	Reporter:	Avihai <aefrat>
Component:	Frontend.WebAdmin	Assignee:	Ahmad Khiet <akhiet>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shir Fishbain <sfishbai>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.2.1	CC:	bugs, frolland, lleistne, tnisan
Target Milestone:	ovirt-4.3.6	Keywords:	EasyFix, StudentProject
Target Release:	4.3.6	Flags:	rule-engine: ovirt-4.3+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-26 19:43:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Avihai 2018-01-10 15:49:41 UTC

Description of problem:
Let's say the storage domain size is 2047G.

Via Webadmin->manage domain window -> change 'Critical space action blocker' to more than the SD size, for example, 3000G  -> this is allowed.

So it's possible to insert a number bigger than storage domain size which does not make sense to me & the system accept this & blocks actions on that SD.

Critical space action blocker value should not be more than the maximum size of the storage domain.


Version-Release number of selected component (if applicable):
4.2.1-0.2.el7

How reproducible:
100%

Steps to Reproduce:
1.Via Webadmin->manage domain window -> change 'Critical space action blocker' to more than the SD size, for example, 3000G  


Actual results:
Critical space action blocker value can be more than the maximum size of the storage domain.

Expected results:
Critical space action blocker value should not be more than the maximum size of the storage domain.

Additional info:

Comment 1 Sandro Bonazzola 2019-01-28 09:40:39 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 2 Shir Fishbain 2019-08-11 13:07:27 UTC

Verified

ovirt-engine-4.3.6-0.1.el7.noarch
vdsm-4.30.25-1.el7ev.x86_64

Comment 3 Sandro Bonazzola 2019-09-26 19:43:23 UTC

This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 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.