Bug 1440962 - hammer: when starting new remote execution job, option "--async" is not being respected
Summary: hammer: when starting new remote execution job, option "--async" is not being...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard: scale_lab
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-10 20:36 UTC by Jan Hutař
Modified: 2019-08-12 15:58 UTC (History)
13 users (show)

Fixed In Version: tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:07:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19251 0 None None None 2017-04-12 06:53:14 UTC

Description Jan Hutař 2017-04-10 20:36:44 UTC 
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.
Comment 2 Adam Ruzicka 2017-04-12 06:53:05 UTC 
Created redmine issue http://projects.theforeman.org/issues/19251 from this bug
Comment 3 Satellite Program 2017-04-12 08:17:01 UTC 
Upstream bug assigned to aruzicka
Comment 4 Satellite Program 2017-04-12 08:17:06 UTC 
Upstream bug assigned to aruzicka
Comment 5 Satellite Program 2017-04-19 12:17:24 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19251 has been resolved.
Comment 7 Adam Ruzicka 2017-08-16 14:32:46 UTC 
The fix is included in upstream release hammer_cli_foreman_remote_execution-0.0.6
Comment 8 yuk 2017-09-15 08:25:41 UTC 
Has hammer_cli_foreman_remote_execution-0.0.6 been released?
Comment 9 Bryan Kearney 2017-09-15 13:17:50 UTC 
We will be releasing this version with Satellite 6.3.
Comment 10 Bryan Kearney 2017-09-27 18:19:30 UTC 
Resetting the needinfo flag since it was provided in https://bugzilla.redhat.com/show_bug.cgi?id=1440962#c9
Comment 11 Peter Ondrejka 2017-10-16 12:18:53 UTC 
Checking on satellite-6.3.0-20.0.beta.el7sat.noarch, --async still not accepted, progress bar shown and blocking cli as described in problem description.

Changes possibly not downstream yet?
~]# rpm -qa | grep remote
tfm-rubygem-foreman_remote_execution_core-1.0.6-1.fm1_15.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5-3.fm1_15.el7sat.noarch
tfm-rubygem-foreman_remote_execution-1.3.6-1.fm1_15.el7sat.noarch
rubygem-smart_proxy_remote_execution_ssh-0.1.6-1.el7sat.noarch
Comment 14 Peter Ondrejka 2017-10-23 12:42:46 UTC 
Verified on satellite-6.3.0-21.0.beta.el7sat.noarch
Comment 15 Bryan Kearney 2018-02-21 17:07:09 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.