Bug 1926082 - Insights operator should not go degraded during upgrade
Summary: Insights operator should not go degraded during upgrade
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Insights Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Tomas Remes
QA Contact: Pavel Šimovec
Depends On:
Blocks: 1925659
TreeView+ depends on / blocked
Reported: 2021-02-08 07:37 UTC by Tomas Remes
Modified: 2021-07-27 22:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1925659
Last Closed: 2021-07-27 22:42:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift insights-operator pull 332 0 None open Bug 1926082: Relax the recent log gatherers to avoid degrading during… 2021-02-08 07:40:41 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:42:37 UTC

Description Tomas Remes 2021-02-08 07:37:50 UTC
+++ This bug was initially created as a clone of Bug #1925659 +++


    ClusterOperators did not settle: 
    clusteroperator/insights is Degraded for 17m19.717543653s because "Source clusterconfig could not be retrieved: Get \"\": dial tcp connect: connection refused, Get \"\": dial tcp connect: connection refused"

The insights operator is not allowed to go degraded and block a cluster upgrade because of failures in gathering data from other components.

The failure that caused this will be independently debugged, insights is not allowed to go degraded because of a failure to gather data from one specific subsystem.

--- Additional comment from Clayton Coleman on 2021-02-05 20:05:43 UTC ---

Especially transient errors.

--- Additional comment from Clayton Coleman on 2021-02-05 20:39:04 UTC ---

This is happening in about 1% of upgrades


It looks like the symptom is fairly similar, but the correct behavior is not "hide this one failure from causing degraded" it is "don't degrade at all if not all data can be gathered".

--- Additional comment from Tomas Remes on 2021-02-08 07:23:21 UTC ---

OK. I didn't know this. Yes we parse some logs (sdn, sdn-controller and some more) for interesting messages and these are very likely not ready yet. I think the fix should be pretty easy. I am about to open a PR.

Comment 3 errata-xmlrpc 2021-07-27 22:42:10 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.8.2 bug fix and 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.