Bug 1630294 - [RFE] Remote execution overview dashboard should be more interactive like the Monitor Dashboard
Summary: [RFE] Remote execution overview dashboard should be more interactive like the...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.4
Hardware: x86_64
OS: Linux
low
low
Target Milestone: 6.13.0
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
: 1549693 2004481 2153582 (view as bug list)
Depends On:
Blocks: 1122832 1619394
TreeView+ depends on / blocked
 
Reported: 2018-09-18 10:32 UTC by Mihir Lele
Modified: 2023-09-07 19:23 UTC (History)
13 users (show)

Fixed In Version: foreman_remote_execution-8.2.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:20:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (44.09 KB, image/png)
2018-09-18 10:32 UTC, Mihir Lele
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22714 0 Normal New Guide user in filtering options in job detail page 2021-02-03 09:57:45 UTC
Foreman Issue Tracker 24962 0 Low New Remote execution overview dashboard should be more interactive like the Monitor Dashboard 2021-02-03 09:57:45 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:20:49 UTC

Description Mihir Lele 2018-09-18 10:32:47 UTC
Created attachment 1484332 [details]
screenshot

Description:

Remote execution overview dashboard should be more interactive like the Monitor Dashboard. We can use the icons under the pie chart to filter hosts based on their status. 

For example: If we click on the "Red (x)", it should display only the hosts that failed to execute the job and filter out rest of the hosts. This is similar to what we can do with the Monitor Dashboard for the hosts reported through puppet.

Version: 6.4 HTB

Additional info:

Attaching screenshot for more clarity

Comment 1 Adam Ruzicka 2018-09-18 12:05:07 UTC
Created redmine issue http://projects.theforeman.org/issues/24962 from this bug

Comment 2 Peter Vreman 2018-09-20 08:31:27 UTC
BZ https://bugzilla.redhat.com/show_bug.cgi?id=1549693 is the same request based on the Sat6.2 pages. I think that old one can be closed as htis new describes it better and is 'rebased' against the current sat6.4

Comment 3 Bryan Kearney 2018-09-27 17:10:31 UTC
*** Bug 1549693 has been marked as a duplicate of this bug. ***

Comment 4 Satellite Program 2018-09-27 17:11:09 UTC
Connecting redmine issue https://projects.theforeman.org/issues/22714 from this bug

Comment 5 Adam Ruzicka 2018-10-03 11:46:33 UTC
Agreed, BZ1549693 was closed and marked as a duplicate of this one.

Comment 10 Peter Vreman 2021-05-03 07:34:18 UTC
With Sat6.8 the UX inconsistency is still there on the Job status Pie Chart:
- The browser shows the pointer cursor (the hand) that the item is clickable
- Clicking , but nothing is happening.

Based on this incorrect behaviour this BZ is really a Bug and not just another RFE.
What is the difficulty here that the click changes the URL to filter only on the status?

Comment 18 Adam Ruzicka 2023-01-02 14:23:14 UTC
*** Bug 2153582 has been marked as a duplicate of this bug. ***

Comment 24 Adam Ruzicka 2023-01-18 15:14:17 UTC
The changes were picked into foreman_remote_execution-8.2.0.

Comment 27 Peter Ondrejka 2023-01-23 13:26:38 UTC
Verified on Satellite 6.13 snap 7, the chart in job details is interactive and triggers filtering in the hosts table

Comment 29 Marek Hulan 2023-03-02 09:38:03 UTC
*** Bug 2004481 has been marked as a duplicate of this bug. ***

Comment 32 errata-xmlrpc 2023-05-03 13:20:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.13 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2097


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