Bug #19251

hammer: when starting new remote execution job, option "--async" is not being respected

Added by Adam Ruzicka about 1 year ago. Updated about 1 year ago.

Assigned To:Adam Ruzicka
Target version:Foreman - Team Ivan Iteration 13
Difficulty: Pull request:https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/14
Bugzilla link:1440962
Story points-
Velocity based estimate-


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):

How reproducible:

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.

Associated revisions

Revision 16afbcc3
Added by adamruzicka about 1 year ago

Fixes #19251 - Honor async flag when creating job invocation (#14)

  • Fixes #19251 - Honor async flag


#1 Updated by Adam Ruzicka about 1 year ago

  • Category set to CLI
  • Assigned To set to Adam Ruzicka
  • Target version set to Team Ivan Iteration 13

#2 Updated by The Foreman Bot about 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/14 added

#3 Updated by Anonymous about 1 year ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF