Actions
Bug #20674
closedShowing job invocation in context of different organization that it was run against breaks the status chart
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1481994
Version-Release number of selected component (if applicable):
Sat 6.3 snap 11
How reproducible:
always
Steps to Reproduce:
1. run job invocation in OrgA
2. switch context to OrgB
Actual results:
The status chart fails to render, stating "Infinity%
Failed"
Empty list of hosts in hosts table.
Expected results:
The chart should render correctly regardless of org context
The empty table uses a placeholder explaning that it shows
only hosts form current context.
Additional info:
Updated by Ivan Necas over 6 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 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 Adam Ruzicka almost 4 years ago
- Is duplicate of Bug #22187: when I delete hosts where remote job was running, that finished remote job will start showing >100% result added
Updated by Adam Ruzicka almost 4 years ago
- Status changed from New to Duplicate
- Triaged set to No
Actions