Exception thrown by beaker cli task watchdog-extend, when e.g. job ID is entered instead of task ID, is little bit confusing. The exception is Exception: bkr.server.bexceptions.BX:'No watchdog exists for recipe 12345' suggesting, that recipe ID should be entered (correct is to enter task ID).
Bulk reassignment of issues as Bill has moved to another team.
reproduced on beaker-devel Version - 0.13.2 steps: #bkr watchdog-extend 789(job ID) XML-RPC fault: <class 'bkr.common.bexceptions.BX'>:'No watchdog exists for recipe 311'
For consistency with all the other client commands, bkr watchdog-extend would ideally accept a "taskspec" style argument giving either a recipe (R:123) or a recipe-task (T:123). That makes things a bit less ambiguous, and lets us giving better a clearer error. We will have to continue accepting unqualified task ID for compatibility as well though.
(In reply to Dan Callaghan from comment #5) > and lets us giving better a clearer error. Wow... I will make the error message clearer than that, I promise!
Is this fixed by bug 1103582?
(In reply to Dan Callaghan from comment #7) > Is this fixed by bug 1103582? Indeed it is. Output is now: $ bkr watchdog-extend 999999999999 HTTP error: 404 Client Error: NOT FOUND 999999999999 is not a valid RecipeTask id
Beaker 21.0 has been released.