Project

General

Custom queries

Profile

Actions
Copy link

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.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_remote_execution/pull/468, https://github.com/theforeman/foreman_remote_execution/pull/472
Fixed in Releases:
foreman_remote_execution 3.1.0
Found in Releases:
Red Hat JIRA:

Description

One option would be to make the data about taxonomies, part of targeting and show it there.

Related issues 3 (0 open — 3 closed)

Related to Foreman Remote Execution - Bug #24882: recurring jobs ignore organization context of host searchClosedActions
Related to Foreman Remote Execution - Bug #20674: Showing job invocation in context of different organization that it was run against breaks the status chartDuplicateActions
Related to Foreman Remote Execution - Feature #25149: Re-run of the job should allow to use the same taxonomy as previous jobClosedActions
Actions
Copy link
 #2

Updated by Marek Hulán over 6 years ago

Other option is to load it from the task.

Actions
Copy link
 #5

Updated by Ivan Necas over 6 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.

Actions
Copy link
 #8

Updated by Leos Stejskal over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF