Bug #25144
closed
The job invocation details should show in which context (organization, location) it has been run
Added by Ivan Necas over 6 years ago.
Updated about 5 years ago.
Description
One option would be to make the data about taxonomies, part of targeting and show it there.
- Related to Bug #24882: recurring jobs ignore organization context of host search added
Other option is to load it from the task.
- Related to Bug #20674: Showing job invocation in context of different organization that it was run against breaks the status chart added
- Related to Feature #25149: Re-run of the job should allow to use the same taxonomy as previous job added
Yes, however the problem with that approach is that the data from there are harder to use outside of the invocation itself, and I wound not recommend this pattern in general. See also #20674 and #25149, that should be also considered when implementing solution and it looks like we need more first-class support for taxonomies rex.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/468 added
- Fixed in Releases foreman_remote_execution 3.0.2 added
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/472 added
- Fixed in Releases foreman_remote_execution 3.1.0 added
- Fixed in Releases deleted (
foreman_remote_execution 3.0.2)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by