Elasticsearch Operator logs shows "index_not_found_exception"

Solution Verified - Updated -

Issue

  • Elasticsearch Operator logs shows "index_not_found_exception" as below:

    2024-05-05T19:35:14.488479888Z {"_ts":"2024-05-05T19:35:14.48833459Z","_level":"0","_component":"elasticsearch-operator_controllers_Elasticsearch","_message":"Failed to initialize first index alias for mapping","_error":{"cluster":"elasticsearch","msg":"failed to update aliases","namespace":"openshift-logging","response_body":{"error":{"index":"app-000001","index_uuid":"_na_","reason":"no such index","resource.id":"app-000001","resource.type":"index_or_alias","root_cause":[{"index":"app-000001","index_uuid":"_na_","reason":"no such index","resource.id":"app-000001","resource.type":"index_or_alias","type":"index_not_found_exception"}],"type":"index_not_found_exception"},"status":404},"response_error":null,"response_status":404},"cluster":"elasticsearch","handler":"indexmanagement","mapping":"app","name":"app","namespace":"openshift-logging"}
    

Environment

  • Red Hat OpenShift Container Platform
    • 4
  • Red Hat OpenShift Logging
    • 5
  • Elasticsearch

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