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:
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.
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
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.
On Gerrit: http://gerrit.beaker-project.org/#/c/4270/
(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/
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.
Beaker 21.0 has been released.