Project

General

Profile

Actions

Bug #20674

closed

Showing job invocation in context of different organization that it was run against breaks the status chart

Added by Adam Ruzicka over 6 years ago. Updated about 3 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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:


Related issues 3 (0 open3 closed)

Related to Foreman Remote Execution - Feature #25149: Re-run of the job should allow to use the same taxonomy as previous jobClosedActions
Related to Foreman Remote Execution - Bug #25144: The job invocation details should show in which context (organization, location) it has been runClosedActions
Is duplicate of Foreman Remote Execution - Bug #22187: when I delete hosts where remote job was running, that finished remote job will start showing >100% resultClosedActions
Actions #1

Updated by Adam Ruzicka over 6 years ago

  • Target version set to 113
Actions #2

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
Actions #3

Updated by Ivan Necas over 5 years ago

  • Related to Bug #25144: The job invocation details should show in which context (organization, location) it has been run added
Actions #4

Updated by Adam Ruzicka about 3 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
Actions #5

Updated by Adam Ruzicka about 3 years ago

  • Status changed from New to Duplicate
  • Triaged set to No
Actions

Also available in: Atom PDF