Bug #19251
closedhammer: when starting new remote execution job, option "--async" is not being respected
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1440962
Description of problem:
when starting new remote execution job via hammer, option "--async" is not being respected
Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.5.1.13-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5.3-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. # hammer --username admin --password changeme job-invocation create --async --description-format "TODO" --inputs command=date --job-template "Run Command - SSH Default" --search-query 'name ~ r630 AND name !~ c10-h31 AND name !~ c10-h32 AND name !~ c10-h33 AND name ~ container700'
(I assume that search query is not part of the reproducer)
Actual results:
There is ID shown and then a progress bar, command does not return and I have to press Ctrl+C
Expected results:
Command should show ID and then exit.
Updated by Adam Ruzicka over 7 years ago
- Category set to CLI
- Assignee set to Adam Ruzicka
- Target version set to 1.12.4
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/14 added
Updated by Anonymous over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset hammer_cli_foreman_remote_execution|16afbcc36c3d72d3e1cae1cf8cee735298fb29d4.