Bug 1988282

Summary: (release-4.7] Operator operation is not set when updating status
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Insights OperatorAssignee: Tomas Remes <tremes>
Status: CLOSED WONTFIX QA Contact: Dmitry Misharov <dmisharo>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, inecas, mklika, tremes
Target Milestone: ---   
Target Release: 4.7.z   
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: 2021-10-08 13:10:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1983247    
Bug Blocks: 1982174    

Description OpenShift BugZilla Robot 2021-07-30 09:18:01 UTC
+++ This bug was initially created as a clone of Bug #1983247 +++

+++ This bug was initially created as a clone of Bug #1982170 +++

Description of problem:
Operator operation is not set when updating status. This can lead to undesired "degraded" state of the Insights Operator when some of the important gatherers fail. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tomas Remes 2021-10-08 13:10:10 UTC
This was already addressed with https://github.com/openshift/insights-operator/commit/19b13a7cf1bd5f38a4f1bc4f257ff7fd70803093