Project

General

Profile

Actions
Copy link

Bug #19251

closed

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

Added by Adam Ruzicka over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Low
Assignee:
Adam Ruzicka
Category:
CLI
Target version:
1.12.4
Difficulty:
Triaged:
Bugzilla link:
1440962
Pull request:
https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/14
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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.

Actions
Copy link

Also available in: Atom PDF