Major The customer has 4 SMCPs installed and for one SMCP the traces are not generating.
The SMCP having the issue is installed in "gfor-core-istio" NS.
Gateway & VS Namespace: pruebashttps-gfor-gateway
Service mesh must-gather: https://attachments.access.redhat.com/hydra/rest/cases/03479115/attachments/56d48b7b-07e4-4a9b-b37a-df5fbf4cdbcf?usePresignedUrl=true
Below are the operator versions:
$ oc get csv NAME DISPLAY VERSION REPLACES PHASE devworkspace-operator.v0.19.1-0.1682321189.p DevWorkspace Operator 0.19.1+0.1682321189.p devworkspace-operator.v0.18.1-0.1675929565.p Succeeded dynatrace-operator.v0.11.2 Dynatrace Operator 0.11.2 dynatrace-operator.v0.11.1 Succeeded elasticsearch-operator.v5.6.5 OpenShift Elasticsearch Operator 5.6.5 elasticsearch-operator.v5.6.4 Succeeded ibm-automation-core.v1.3.13 IBM Automation Foundation Core 1.3.13 ibm-automation-core.v1.3.8 Succeeded ibm-common-service-operator.v3.19.11 IBM Cloud Pak foundational services 3.19.11 ibm-common-service-operator.v3.19.3 Succeeded ibm-eventstreams.v3.1.6 IBM Event Streams 3.1.6 ibm-eventstreams.v3.0.5 Succeeded ibm-integration-platform-navigator.v6.0.9 IBM Cloud Pak for Integration 6.0.9 ibm-integration-platform-navigator.v5.3.2 Succeeded jaeger-operator.v1.42.0-5 Red Hat OpenShift distributed tracing platform 1.42.0-5 jaeger-operator.v1.39.0-3 Succeeded kiali-operator.v1.57.7 Kiali Operator 1.57.7 kiali-operator.v1.57.6 Succeeded servicemeshoperator.v2.3.3 Red Hat OpenShift Service Mesh 2.3.3-0 servicemeshoperator.v2.3.2 Succeeded web-terminal.v1.5.1-0.1661829403.p Web Terminal 1.5.1+0.1661829403.p web-terminal.v1.5.0-0.1657724953.p Succeeded
