+++ This bug was initially created as a clone of Bug #2185188 +++ Description of problem (please be detailed as possible and provide log snippests): Fix the issue where OCSInitialization adds its own name to the storage cluster request queue when there is a change in it. Modify the code to enqueue the storage cluster name instead. ocs-operator logs: {"level":"info","ts":"2023-04-05T06:54:29Z","logger":"controllers.StorageCluster","msg":"No StorageCluster resource.","Request.Namespace":"openshift-storage","Request.Name":"ocsinit","StorageCluster":{"name":""}}
Verifications Steps: We should not see a request for a storagecluster reconciliation named ocsinit as shown in the above logs of ocs-operator.
A backport is necessary because a regression was introduced while fixing other bugs. This regression causes the storage cluster reconcile process to requeue the OCS initialization resource as a storage cluster resource. However, the reconciler complains that the resource does not exist, which results in the reconcile process being skipped whenever there is an update in the configmap.
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 (Red Hat OpenShift Data Foundation 4.11.8 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-2023:3293