Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-4831

CRD metrics cannot be scraped when the OpenTelemetry Operator is not installed in the openshift-opentelemetry-operator namespace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • rhosdt-3.5
    • None
    • OpenTelemetry
    • None
    • Tracing Sprint # 261, Tracing Sprint # 262

      Description:
      When the Red Hat build of OpenTelemetry operator is not installed in the default namespace of openshift-opentelemetry-operator, metrics collection will fail even if the openshift.io/cluster-monitoring: "true" label exists on the namespace that it has been installed in. 

      Additionally the following TargetDown alerts are visible in the OpenShift Web Console:

      • 100% of the opentelemetry-operator-webhook-service/opentelemetry-operator-webhook-service targets in <installed-namespace> namespace have been unreachable for more than 15 minutes. 
      • 100% of the opentelemetry-operator-controller-manager-metrics-service/opentelemetry-operator-controller-manager-metrics-service targets in Namespace <installed-namespace> have been unreachable for more than 15 minutes.

      Environment: 
      opentelemetry-operator.v0.107.0-4-0.1727168137.p

      Reproduction Steps:

      1. Create a namespace. This namespace can't have the name of openshift-opentelemetry-operator. 
      2. Add the label openshift.io/cluster-monitoring: "true" to this namespace.
      3. Install the operator as normal.

      Workaround:

      Uninstall the operator and reinstall it in the openshift-opentelemetry-operator namespace. 

              rhn-support-iblancas Israel Blancas Alvarez (Inactive)
              rhn-support-cuthayak Clark Uthayakumar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: