Deleting elasticsearch CR errors when not installed Elasticsearch Operator in RHOCP4
Issue
-
When only installed the ClusterLogging Operator (CLO) for log forwarding the logs to external outputs, the CLO operator returns continually the error log:
$ oc logs $(oc get pod -l name=cluster-logging-operator -o name) |grep "Failure deleting elasticsearch elasticsearch CR" |head -1 {"_ts":"2023-03-13T09:13:10.794416893Z","_level":"0","_component":"cluster-logging-operator","_message":"Error removing component","_error":{"msg":"Failure deleting elasticsearch elasticsearch CR for \"instance\": no matches for kind \"Elasticsearch\" in version \"logging.openshift.io/v1\""}}
-
When only installed the CLO since not needed the Elasticsearch Operator (EO), the CLO pod is throwing the error
"Failure deleting elasticsearch elasticsearch CR"
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Logging (RHOL)
- 5.6
- ClusterLogging Operator (CLO)
- Elasticsearch Operator (EO)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.