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

Bug 2080964

Summary: Cluster operator special-resource-operator is always in Failing state with reason: "Reconciling simple-kmod"
Product: OpenShift Container Platform Reporter: Udi Kalifon <ukalifon>
Component: Special Resource OperatorAssignee: Quentin Barrand <quba>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.10CC: aos-bugs
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:09:50 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 Udi Kalifon 2022-05-02 13:23:18 UTC
Description of problem:
When deploying the simple-kmod special resource, a cluster operator is created (in addition to the optional operator) and it's always doing reconciliations and always in Failing state. It fires alerts back to OCM.

This bug was previously reported as bug: https://bugzilla.redhat.com/show_bug.cgi?id=2030840


How reproducible:
100%


Steps to Reproduce:
1. Deploy NFD, SRO and the simple-kmod example
2. oc get co


Actual results:
special-resource-operator is in Failing state and never stops reconciling


Expected results:
There is not supposed to be a cluster operator at all, and the reconciliation of simple-kmod should be over.

Comment 2 Udi Kalifon 2022-05-31 13:37:07 UTC
Verified in 4.10.16

Comment 4 errata-xmlrpc 2022-08-10 11:09:50 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