Bug 1387109

Summary:	cannot set power quiescent period to 0 (zero)
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	general	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	dcallagh, huiwang, mjia, rjoost
Target Milestone:	23.3	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-07 06:44:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Callaghan 2016-10-20 07:09:14 UTC

Description of problem:
The default quiescent period is 5, which is a good choice for things like PDU ports. For virtual machines there is no need for any delay, it can be set to zero. But Beaker refuses.

Version-Release number of selected component (if applicable):
23.2

How reproducible:
easy

Steps to Reproduce:
1. Go to system page, Power Settings tab
2. Change quiescent period to 0
3. Hit Save Changes

Actual results:
BAD REQUEST: Quiescent period for power control must be greater than or equal to zero

Expected results:
Should save quiescent period as 0.

Additional info:
Wrong validation condition, change > to >=.

Comment 1 Dan Callaghan 2016-10-20 07:11:04 UTC

http://gerrit.beaker-project.org/5337

Comment 3 Hui Wang 2016-10-21 08:40:45 UTC

Verified this issue. The quiescent period 0 can be saved.
The result is PASS.
Version: beaker-server-24.0.git.143.42e2fdb 
Steps: 
Same with steps in comment#0

Comment 4 Dan Callaghan 2016-11-07 06:44:49 UTC

Beaker 23.3 has been released.