| Summary: | [Beaker] cmdline syntax inconsistent and help is incorrect | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Jeff Burke <jburke> |
| Component: | command line | Assignee: | Bill Peck <bpeck> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.6 | CC: | bpeck, dcallagh, jstancek, mcsontos, pbunyan, rmancy, stl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-03 18:38:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jeff Burke
2011-06-03 15:25:22 UTC
(In reply to comment #0) > Description of problem: > > When using the bkr command line options the syntax between command is not > consistent and the help is not reliable. > > Here are some examples: > > ------------------------------- > $ bkr job-watch --help > Usage: bkr job-watch [options] <taskspec>... > > The above usage should say > Usage: bkr job-watch [options] <jobid>... Why should it say jobid? You say yourself that its not valid below. > ------------------------------- > > ------------------------------- > The inconsistency is when you use job-watch vs watchdog > It is not clear when you need to use a prefix like J: vs T: > > $ bkr job-watch J:84399 > Watching tasks (this may be safely interrupted)... > J:84399 kernel-2.6.18-260.el5.kpq1 KernelTier1: Completed > --> Completed: 1 [total: 1] > > $ bkr job-watch 84399 > Watching tasks (this may be safely interrupted)... > Exception: exceptions.ValueError:need more than 1 value to unpack > > $ bkr watchdog-show T:2053459 > Exception: bkr.server.bexceptions.BX:'Invalid task ID: T:2053459' > > $ bkr watchdog-show 2053459 > 2053459: 85333 > ------------------------------- watchdog-show should be updated to use <taskspec> and we should provide some example taskspecs J:1234 for job and RS:1233 for RecipeSet, etc.. watchdog is a special case - it does not accept anything else but task id. More in Bug 643882. *** This bug has been marked as a duplicate of bug 643882 *** Reply to Comment #1 Q: Why should it say jobid? You say yourself that its not valid below. It is semantics to me if it is jobid or J:jobid but it should reflect what it needs. RE: watchdog-show should be updated to use <taskspec> and we should provide some example taskspecs J:1234 for job and RS:1233 for RecipeSet, etc.. - Thank you |