Feature #25149
closed
Re-run of the job should allow to use the same taxonomy as previous job
Description
Scenario:
1. run a job in a specific org/location
2. select 'any context'
3. re-run the job
Actual result:
- the job gets executed in unlimited scope
- technically, this behaviour is not completely wrong, but it's surprising and can be unexpected: I can have one job that runs against my 10 hosts in specific org/location, and when I re-run the very same job later and I'm not careful, it can run 10000 hosts of my infrastructure
Expected result
1. the default context for the stays the one that was in the original job
2. in case different taxonomy is used in the mean-time, there should be a warning
3. alternatively to 2, we could even prevent showing the job that would be assigned to different taxonomy, basically making the jobs taxable (but ideally with 1:n mapping (as we have in host) as opposed to m:n (as we have in other taxable resources). See also https://projects.theforeman.org/issues/20674
Updated by Ivan Necas over 6 years ago
- Related to Bug #20674: Showing job invocation in context of different organization that it was run against breaks the status chart added
Updated by Ivan Necas over 6 years ago
- Related to Bug #25144: The job invocation details should show in which context (organization, location) it has been run added
Updated by The Foreman Bot about 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/473 added
Updated by The Foreman Bot about 5 years ago
- Fixed in Releases foreman_remote_execution 3.0.2 added
Updated by Leos Stejskal about 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_plugin|1e008cf2ba54cdd797a2dbc71d36c925e63836ab.
Updated by Adam Ruzicka almost 5 years ago
- Fixed in Releases foreman_remote_execution 3.1.0 added
- Fixed in Releases deleted (
foreman_remote_execution 3.0.2)