Bug #17410
closedRerun a job invocation loses the effective user
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1386208
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:
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ivan Necas
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/241 added
Updated by Ivan Necas over 7 years ago
- Target version changed from 113 to 1.12.4
Updated by Ivan Necas over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_plugin|c77cf8606c89e27858498cea8da1b6edb80febff.
Updated by Ivan Necas over 7 years ago
- Translation missing: en.field_release set to 262