Bug 1103582

Summary:	bkr watchdog-extend should accept recipe ID or FQDN as a parameter
Product:	[Retired] Beaker	Reporter:	Amit Saha <asaha>
Component:	general	Assignee:	matt jia <mjia>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.17	CC:	aigao, dcallagh, dowang, ebaak, jburke, jkoten
Target Milestone:	21.0	Keywords:	FutureFeature, Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-26 06:18:07 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:
Bug Depends On:
Bug Blocks:	653317

Description Amit Saha 2014-06-02 07:03:03 UTC

Description of problem:


`bkr watchdog-extend` should accept system FQDNs so that the watchdog for the recipe running on the system can be extended.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Dan Callaghan 2014-11-30 23:44:33 UTC

bkr watchdog-extend really should accept a taskspec (T:123 or R:123) and allow extending the watchdog by either task or recipe. The watchdog is really per-recipe so it doesn't make much sense that we require a task ID right now.

Accepting an FQDN as a shortcut to mean "the recipe running on this system right now" is just a convenience for the <reservesys/> case where the user may care more about the system itself than the recipe.

Comment 3 Jeff Burke 2015-04-07 13:42:57 UTC

Hi Dan,
 I see it moved from 19.2 -> 19.3 then to future_maint. Any thoughts on when it can be fixed. This is one thing that I have been waiting for to integrate with CI.

Thanks,
Jeff

Comment 5 Dan Callaghan 2015-04-08 03:59:21 UTC

Estimate to 5 because this RFE will require us to figure out how our REST API for recipes will look, and in particular a way to map taskspecs and FQDNs back to recipes.

Comment 6 matt jia 2015-06-29 06:43:17 UTC

On Gerrit:

  http://gerrit.beaker-project.org/#/c/4270/

Comment 7 matt jia 2015-07-10 03:32:57 UTC

(In reply to matt jia from comment #6)
> On Gerrit:
> 
>   http://gerrit.beaker-project.org/#/c/4270/

Target this to develop branch.

http://gerrit.beaker-project.org/#/c/4285/

Comment 10 wangdong 2015-07-29 06:44:29 UTC

Verify passed on beaker-client-21.0-0.git.35.ef067a4.el6eng.noarch.rpm

Steps:

1. Create a job and find a taskrecp

2. Use command bkr watchdog-extend T:126965

3. No errors return.

Comment 11 Dan Callaghan 2015-08-26 06:18:07 UTC

Beaker 21.0 has been released.