Bug 1284368

Summary: reserve workflow offers to reserve systems for up to 7 days, but /distribution/reservesys limits to 99 hours
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: generalAssignee: Roman Joost <rjoost>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: dcallagh, dowang, mjia, qzhang, rjoost, tcoufal
Target Milestone: 23.0Keywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-07 23:10:51 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 2015-11-23 07:46:30 UTC 
Steps to Reproduce:
1. Use the reserve workflow to request a system for 7 days
2. Be surprised when the system is reclaimed by Beaker after 4 days 3 hours.

Additional info:
/distribution/reservesys has always enforced a hard limit of 99 hours for the RESERVETIME. This is basically a Red Hat-specific attempt to limit excessive usage of limited lab resources.

However the reserve workflow page allows you to select a reservation time of up to 7 days.

At the very least, the max reserve time offered by reserve workflow should match the limit applied by /distribution/reservesys.

Ideally the limiting would not live in /distribution/reservesys at all (and indeed we are planning to make reserve workflow use <reservesys/> instead) so the maximum watchdog time limit should really be configured in Beaker, and reserve workflow should adjust itself accordingly.
Comment 2 Roman Joost 2016-04-26 06:42:11 UTC 
https://gerrit.beaker-project.org/#/c/4834/1
Comment 5 Dan Callaghan 2016-07-07 23:10:51 UTC 
Beaker 23.0 has been released.
Comment 6 Dan Callaghan 2017-10-23 04:46:55 UTC 
*** Bug 1149132 has been marked as a duplicate of this bug. ***