Bug 1473067
Summary: | bkr workflow-simple example command in documentation errors | |||
---|---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Anwesha Chatterjee <achatter> | |
Component: | command line | Assignee: | Anwesha Chatterjee <achatter> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Dan Callaghan <dcallagh> | |
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | develop | CC: | achatter, dcallagh, mjia, rjoost | |
Target Milestone: | 24.4 | Keywords: | Patch | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1473068 (view as bug list) | Environment: | ||
Last Closed: | 2017-10-03 03:57:54 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
Anwesha Chatterjee
2017-07-20 00:56:51 UTC
version: 24.3-1.fc25 I guess the problem with the example is it assumes you have tasks in your task library which are declared with RunFor: apache or RunFor: tomcat6 So when the example is run against our internal production Beaker instance, that will be the case. But on a freshly created Beaker it won't be. We should probably replace the "--package apache --package tomcat6" options with "--task /some/example/task" so that hopefully it is clear that the command is not supposed to work *as is* out of the box. You would only use it if you have some actual tasks you want to run. We could also improve the error message in the case where the user passes --package, but that doesn't match anything. Right now the error message wording *looks* like a mistake because it's telling you you must pass a package but you *did* pass a package. Maybe print a warning to stderr if a --package option is given but Beaker returns no tasks matching that package? And then we change the error message to be something like: No tasks specified to be run Hint: Use --task, --package, or --type to select tasks *** Bug 1473068 has been marked as a duplicate of this bug. *** This bug fix is included in beaker-client-24.4-0.git.17.9c963d813 which is currently available for download here: https://beaker-project.org/nightlies/release-24/ Verified that the error messages make sense now: $ bkr workflow-simple --dry-run --family RedHatEnterpriseLinux7 --arch x86_64 Usage: bkr workflow-simple [options] bkr: error: No tasks specified to be run Hint: Use --task, --package, --taskfile or --task-type to select tasks $ bkr workflow-simple --dry-run --family RedHatEnterpriseLinux7 --arch x86_64 --package asdfasdf No tasks match the specified option(s) Beaker 24.4 has been released. |