Bug 1901256 - The CLO shouldn't depend on EO resources when deploy collector only clusterlogging instance
Summary: The CLO shouldn't depend on EO resources when deploy collector only clusterl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard: logging-core
Depends On: 1891738
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-24 19:18 UTC by Jeff Cantrill
Modified: 2021-01-25 20:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The cluster-logging-operator tries to reconcile all its managed resources regardless of it being defined or not Consequence: The CLO would attempt to reconcile the elasticsearch resource which was dependent upon the RH provided elastic CRD. Attempts to list an unknown kind will cause the CLO to exit its reconciliation loop Fix: Only reconcile type provided by the elasticsearch-operator if a user defines managed storage. Result: User's can create collector only deployments of cluster logging by only deploying the cluster-logging-operator
Clone Of: 1891738
Environment:
Last Closed: 2021-01-25 20:21:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 814 0 None closed Bug 1901256: Make operator not depend on elasticsearch-operator 2021-01-20 01:46:47 UTC
Red Hat Product Errata RHBA-2021:0173 0 None None None 2021-01-25 20:21:12 UTC

Description Jeff Cantrill 2020-11-24 19:18:14 UTC 
+++ This bug was initially created as a clone of Bug #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:

--- Additional comment from OpenShift Automated Release Tooling on 2020-11-24 18:48:37 UTC ---

Elliott changed bug status from MODIFIED to ON_QA.
Comment 3 Anping Li 2021-01-20 10:33:12 UTC 
Verified on clusterlogging.4.6.0-202101162152.p0
Comment 5 errata-xmlrpc 2021-01-25 20:21:05 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.6.13 extras 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:0173
Note You need to log in before you can comment on or make changes to this bug.