Bug 2004816

Summary: (release-4.9) OCM controller must update operator status
Product: OpenShift Container Platform Reporter: Tomas Remes <tremes>
Component: Insights OperatorAssignee: Tomas Remes <tremes>
Status: CLOSED ERRATA QA Contact: Dmitry Misharov <dmisharo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.9CC: aos-bugs, dmisharo, inecas, mklika, tremes
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2001823 Environment:
Last Closed: 2021-11-10 21:01:58 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: 2001823    
Bug Blocks:    

Comment 2 Dmitry Misharov 2021-11-01 12:43:10 UTC
Verified on 4.9.0-0.nightly-2021-10-30-120753.
Verification steps:
1. Enable TechPreview https://docs.openshift.com/container-platform/4.8/nodes/clusters/nodes-cluster-enabling-features.html
2. Edit "support" secret in "openshift-config" namespace.
   a. Add "ocmEndpoint" key with value "https://httpstat.us/500"
   b. Add "ocmInterval" key with value "1m"
3. Restart Insights Operator
4. Check Insights Cluster Operator status

Operator status is degraded.

Change "ocmEndpoint" to "https://httpstat.us/404" or another status and check cluster operator status. It's not degraded.

Comment 5 errata-xmlrpc 2021-11-10 21:01:58 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 (OpenShift Container Platform 4.9.6 bug fix 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/RHBA-2021:4119