Bug 1481994 - Showing job invocation in context of different organization that it was run against breaks the status chart
Summary: Showing job invocation in context of different organization that it was run a...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-16 08:58 UTC by Ivan Necas
Modified: 2019-08-12 14:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 17:44:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of wrong chart (35.20 KB, image/png)
2017-08-16 08:58 UTC, Ivan Necas
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20674 0 None None None 2017-08-21 12:20:48 UTC

Description Ivan Necas 2017-08-16 08:58:22 UTC
Created attachment 1314017 [details]
screenshot of wrong chart

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:

Comment 2 Adam Ruzicka 2017-08-21 12:20:47 UTC
Created redmine issue http://projects.theforeman.org/issues/20674 from this bug

Comment 3 Bryan Kearney 2018-09-04 17:44:54 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.