Actions
Bug #25144
closed
The job invocation details should show in which context (organization, location) it has been run
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Description
One option would be to make the data about taxonomies, part of targeting and show it there.
Updated by Ivan Necas over 5 years ago
- Related to Bug #24882: recurring jobs ignore organization context of host search added
Updated by Marek Hulán over 5 years ago
Other option is to load it from the task.
Updated by Ivan Necas over 5 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 5 years ago
- Related to Feature #25149: Re-run of the job should allow to use the same taxonomy as previous job added
Updated by Ivan Necas over 5 years ago
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.
Updated by The Foreman Bot about 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/468 added
Updated by The Foreman Bot about 4 years ago
- Fixed in Releases foreman_remote_execution 3.0.2 added
Updated by Leos Stejskal about 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_plugin|942fea05990d23951803b487ea96c5cee856c852.
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/472 added
Updated by Adam Ruzicka about 4 years ago
- Fixed in Releases foreman_remote_execution 3.1.0 added
- Fixed in Releases deleted (
foreman_remote_execution 3.0.2)
Actions