* Previously, the Cluster Logging Operator (CLO) would attempt to reconcile the Elasticsearch resource, which depended upon the Red Hat-provided Elastic Custom Resource Definition (CRD). Attempts to list an unknown kind caused the CLO to exit its reconciliation loop. This happened because the CLO tried to reconcile all of its managed resources whether they were defined or not. The current release fixes this issue. The CLO only reconciles types provided by the Elasticsearch operator if a user defines managed storage. As a result, users can create collector-only deployments of cluster logging by deploying the CLO.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1891738[*BZ#1891738*])
Description of problem:
When deploy collector only clusterlogging instance, the CLO failed to generate fluentd resources.
"error":"Unable to create or update logstore for \"instance\": Failure deleting elasticsearch elasticsearch CR for \"instance\": no matches for kind \"Elasticsearch\" in version \"logging.openshift.io/v1\""
Version-Release number of selected component (if applicable):
4.6
How reproducible:
Always
Steps to Reproduce:
1. Deploy clusterlogging-operator on the fresh cluster which had never deployed elasicsearch operators
2. Create collector only clusterlogging instance
kind: "ClusterLogging"
metadata:
name: "instance"
namespace: openshift-logging
spec:
managementState: "Managed"
collection:
logs:
type: "fluentd"
fluentd: {}
Actual results:
The fluentd resources couldn't be generated.
CLO report error
"error":"Unable to create or update logstore for \"instance\": Failure deleting elasticsearch elasticsearch CR for \"instance\": no matches for kind \"Elasticsearch\" in version \"logging.openshift.io/v1\""
Expected results:
The CLO can generate collector resources.
Additional info:
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 (Errata Advisory for Openshift Logging 5.0.0), 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:0652
Description of problem: When deploy collector only clusterlogging instance, the CLO failed to generate fluentd resources. "error":"Unable to create or update logstore for \"instance\": Failure deleting elasticsearch elasticsearch CR for \"instance\": no matches for kind \"Elasticsearch\" in version \"logging.openshift.io/v1\"" Version-Release number of selected component (if applicable): 4.6 How reproducible: Always Steps to Reproduce: 1. Deploy clusterlogging-operator on the fresh cluster which had never deployed elasicsearch operators 2. Create collector only clusterlogging instance kind: "ClusterLogging" metadata: name: "instance" namespace: openshift-logging spec: managementState: "Managed" collection: logs: type: "fluentd" fluentd: {} Actual results: The fluentd resources couldn't be generated. CLO report error "error":"Unable to create or update logstore for \"instance\": Failure deleting elasticsearch elasticsearch CR for \"instance\": no matches for kind \"Elasticsearch\" in version \"logging.openshift.io/v1\"" Expected results: The CLO can generate collector resources. Additional info: