Bug 1162500

Summary:	[RFE] Allow dynamic updates to server managed recipe reservations
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	general	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	azelinka, dcallagh, ebaak, rjoost
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-01 13:15:53 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 Nick Coghlan 2014-11-11 07:50:44 UTC

Beaker 0.17 added support for harness independent system reservations after a recipe is completed or aborted. As these are managed by the server, they could be made configurable via the web UI and bkr CLI for a previously submitted recipe.

The kinds of cases where that feature seems potentially interesting are:

* After manually kicking a recipe that stalled for some reason (the case
that prompted the idea)
* After noticing something odd in the execution of a long running recipe
* Switching from "always" to "only on failure" if you forget to make it
conditional (or vice-versa)
* Adding or removing the reservation request if you simply made a mistake at
submission time

Rather than building this into the current job details page, it is suggested to consider this proposal further after that page has been redesigned (tentatively under consideration for Beaker 20 in early 2015).

Comment 1 Dan Callaghan 2016-06-01 13:15:53 UTC


*** This bug has been marked as a duplicate of bug 1340141 ***