-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of the issue:
When a ObservabilityInstaller CR instance is deleted with spec.capabilites.tracing.operators.install: true, only the subscription for the operators is deleted. We should also delete the associated CSV and CRDs of the operators.
Steps to reproduce the issue:
*Create the following ObservabilityInstaller instance.
apiVersion: observability.openshift.io/v1alpha1 kind: ObservabilityInstaller metadata: name: test-operator-install spec: capabilities: tracing: operators: install: true
*Delete the CR instance and check that the subscription of the Tempo and OpenTelemetry operator is deleted but the CSV and CRDs are still present. If we try to install the operators again it creates conflict as the CSVs from previous install is present.
% oc delete -f operator-instal.yaml observabilityinstaller.observability.openshift.io "test-operator-install" deleted % oc get sub NAME PACKAGE SOURCE CHANNEL observability-operator-v1-2-5-sub observability-operator observability-operator-catalog operator-sdk-run-bundle % oc get csv NAME DISPLAY VERSION REPLACES PHASE observability-operator.v1.2.5 Observability Operator 1.2.5 Succeeded opentelemetry-operator.v0.135.0-1 Red Hat build of OpenTelemetry 0.135.0-1 opentelemetry-operator.v0.127.0-2 Succeeded tempo-operator.v0.18.0-1 Tempo Operator 0.18.0-1 tempo-operator.v0.16.0-2 Succeeded % oc get customresourcedefinitions.apiextensions.k8s.io| grep -iE "tempo|opentelemetry" instrumentations.opentelemetry.io 2025-10-06T06:42:58Z opampbridges.opentelemetry.io 2025-10-06T06:42:58Z opentelemetrycollectors.opentelemetry.io 2025-10-06T06:42:58Z targetallocators.opentelemetry.io 2025-10-06T06:42:59Z tempomonolithics.tempo.grafana.com 2025-10-06T06:43:02Z tempostacks.tempo.grafana.com 2025-10-06T06:43:02Z
