Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2059586

Summary:	(release-4.11) Insights operator doesn't reconcile clusteroperator status condition messages
Product:	OpenShift Container Platform	Reporter:	Tomas Remes <tremes>
Component:	Insights Operator	Assignee:	Tomas Remes <tremes>
Status:	CLOSED ERRATA	QA Contact:	Joao Fula <jfula>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	aos-bugs, inecas, mklika, tremes
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 10:51:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Remes 2022-03-01 12:06:18 UTC

Description of problem:


Insights operator doesn't set the default messages and doesn't reconcile them for the following clusteroperator status conditions: Available, Progressing, Degraded and Upgradeable. 


How reproducible:


It's basically the output of "oc get co insights -o json | jq .status.conditions" and you have to change some message programmatically to reproduce this problem.

Actual results:

The updated message remains the same. 


Expected results:

The updated message should be reconciled to the original value after some time.


Additional info:

Comment 2 Joao Fula 2022-03-08 07:32:13 UTC

Changes were reverted in: https://github.com/openshift/insights-operator/pull/586
Moving back to POST state.

Comment 4 Joao Fula 2022-03-09 08:43:01 UTC

Verified on 4.11.0-0.ci-2022-03-08-235257.

Verification steps:
1. Run script to change status conditions messages.

2. Run 
oc get co insights -o json | jq .status.conditions 
message should contain "operator is expected to reconcile this message"

3. Within 2 minutes, messages should automatically be reconciled to their original value.
Check by rerunning the command on step 2.

Comment 5 Joao Fula 2022-03-14 11:03:52 UTC

New issue detected. Reverting to status NEW.

Comment 7 Joao Fula 2022-03-21 16:24:34 UTC

Verified on 4.11.0-0.nightly-2022-03-20-160505.

Verification steps:
1. Run script to change status conditions messages.

2. Run 
oc get co insights -o json | jq .status.conditions 
message should contain "operator is expected to reconcile this message"

3. Within 2 minutes, messages should automatically be reconciled to their original value.
Check by rerunning the command on step 2.

Comment 9 errata-xmlrpc 2022-08-10 10:51:27 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: OpenShift Container Platform 4.11.0 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.

https://access.redhat.com/errata/RHSA-2022:5069