Elasticsearch Operator failing to get index settings errors with jaeger indices

Solution Verified - Updated -

Issue

  • The Elasticsearch Operator (EO) is failing to get index settings from Jaeger indices with errors like:

    {"_ts":"2021-10-15T12:03:30.72868073Z","_level":"0","_component":"elasticsearch-operator","_message":"failed to get index settings","_error":{"cause":{"Value":"string","Type":{},"Offset":81,"Struct":"IndexMapperSettings","Field":"settings.index.mapper.dynamic"},"destination_type":"estypes.IndexSettings","index":"jaeger-service-2021-10-15","msg":"failed to decode response body"},"cluster":"elasticsearch","index":"jaeger-service-2021-10-15","namespace":"service-mesh"}
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat Openshift Logging (RHOL)
    • 5
  • Red Hat OpenShift Service Mesh

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content