Description of problem: the effective user field is not included when a job is being rerun. This is even more tricky, because it is not directly visible from the the new job invocation page because the effective user is hidden in the advanced fields that are by default collapsed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Run a job template with effective user root 2. Rerun the job template 3. Actual results: The rerun of job template does not run with effective user root Expected results: The rerun job template runs with effective user root Additional info:
Created redmine issue http://projects.theforeman.org/issues/17410 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/17410 has been resolved.
Verified. Satellite-6.3 Snap 9 Package versions: satellite-6.3.0-16.0.beta.el7sat.noarch tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_15.el7sat.noarch 1) Set effective user to toor 2) Run the job 3) Rerun the job 4) Effective user for the new job is toor
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