Bug 1600673 - Exclude "Hosts with alerts disabled" from showing in the Host Configuration Chart in Satellite Dashboard
Summary: Exclude "Hosts with alerts disabled" from showing in the Host Configuration C...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dashboard
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.6.0
Assignee: satellite6-bugs
QA Contact: Apurva
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-12 18:18 UTC by Prajeesh
Modified: 2021-09-09 15:00 UTC (History)
6 users (show)

Fixed In Version: foreman-1.22.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:51:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Dashboard (108.54 KB, image/png)
2019-06-27 16:59 UTC, Apurva 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24396 0 Normal Closed Wrong search on alert-disabled hosts 2020-02-28 14:25:29 UTC

Comment 2 Marek Hulan 2018-07-26 13:02:54 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/24396 from this bug
Comment 3 Bryan Kearney 2019-02-07 09:09:32 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24396 has been resolved.
Comment 4 Apurva 2019-06-27 16:59:16 UTC 
Created attachment 1585294 [details]
Dashboard

Verified

Verified on: Satellite 6.6.0 snap 7

Steps:
1. Hosts -> All hosts -> select 1-2 hosts -> Select Action -> Disable Notifications
2. Monitor -> Dashboard


Observation:
the hypervisor is excluded in the "Host Configuration Chart"
Comment 6 Bryan Kearney 2019-10-22 19:51:57 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, 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.