Bug 2039868 - Insights Advisor widget is not in the disabled state when the Insights Operator is disabled
Summary: Insights Advisor widget is not in the disabled state when the Insights Operat...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Insights Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Georgii Karataev
QA Contact: ireyes
Depends On:
Blocks: 2066771
TreeView+ depends on / blocked
Reported: 2022-01-12 15:27 UTC by Georgii Karataev
Modified: 2022-03-22 16:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:39:13 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10826 0 None open Bug 2039868: Enhance Insights widget empty states 2022-01-12 15:37:15 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:39:26 UTC

Description Georgii Karataev 2022-01-12 15:27:05 UTC
Once administrators have opted out of remote health reporting and disabled Insights Operator for their cluster (removing the "cloud.openshift.com" token from the pull-secret - see https://docs.openshift.com/container-platform/4.9/support/remote_health_monitoring/opting-out-of-remote-health-reporting.html), the Prometheus query

"cluster_operator_conditions{name="insights", condition="Disabled"}"

results in `1` (true), which means that the Insights Operator is disabled.

However, the Insights Advisor widget in the main dashboard still shows Insights rule results in the main dashboard for some time. The Insights Advisor widget must consume this Prometheus metric to learn whether Insights Operator is disabled and show the "Disabled" message as long as the Prometheus query results in 1 (true).

Comment 3 ireyes 2022-01-24 09:46:12 UTC
Verified using a 4.10 cluster-bot cluster and using master branch of openshift-console on a 4.8 cluster

Comment 6 errata-xmlrpc 2022-03-10 16:39:13 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

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


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