Description of problem: Error initializing command: RuntimeError - Unable to upload file to /var/tmp/foreman-ssh-cmd-c8506e1b-558d-45a1-a8b5-b4a1c77d7fd3/script on remote system: exit code: 127 Version-Release number of selected component (if applicable): tfm-rubygem-remote-execution-core 1.0.3 How reproducible: always Steps to Reproduce: 1. run job with non-root effective user Actual results: The jobs fails with 'Error initializing command: RuntimeError - Unable to upload file to /var/tmp/foreman-ssh-cmd-c8506e1b-558d-45a1-a8b5-b4a1c77d7fd3/script on remote system: exit code: 127' as the result Expected results: job doesn't fail with this error Additional info: This is a regression introduced in https://bugzilla.redhat.com/show_bug.cgi?id=1389262
Created redmine issue http://projects.theforeman.org/issues/19575 from this bug
Upstream bug assigned to inecas
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19575 has been resolved.
Created attachment 1316962 [details] verification screenshot
Verified. Version Tested: Satellite-6.3 Snap 12 Package versions: satellite-6.3.0-16.0.beta.el7sat.noarch tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_15.el7sat.noarch tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_15.el7sat.noarch Ran a job on a remote host with effective user set, the job finished successfully. See attachment in #6.
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