Description of problem: The Service Telemetry Operator (STO) can error out when working on systems with the ECK (Elastic Cloud on Kubernetes) Operator installed. Version-Release number of selected component (if applicable): STF 1.2 How reproducible: Consistent Steps to Reproduce: Install STO without ECK and deploy a `ServiceTelemetry` object. Because the STO tries to make sure the `ElasticSearch` object is present or absent, it does an object lookup, which can result in a failure. Additional info: See https://github.com/infrawatch/service-telemetry-operator/blob/master/roles/servicetelemetry/tasks/component_elasticsearch.yml#L12 which does not have a `when` clause. The issue with the `when` clause is if you set it to look for `backends.elasticsearch.enabled is true` then it will not drop the ElasticSeach object should you ever move from `true` to `false. The error you would see is `Failed to find exact match for elasticsearch.k8s.elastic.co/v1beta1.Elasticsearch` The TODO indicates we should set the appropriate permissions so that we can do a lookup to determine if the CRD exists, and if it does, then we can continue with the `absent` and `present` lookups.
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 (Moderate: Release of components for Service Telemetry Framework 1.3.3 - Container Images), 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-2021:4582