The elasticsearch-im-xxx job fails when trying to start the index management process for a non-existing index

Solution In Progress - Updated -

Issue

  • The following logs can be seen in the logs of the elasticsearch-im-xxx-xxxxx pods that are in Error status.

    2021-07-25T05:15:12.824232244Z Index management delete process starting for {"error":{"root_cause":[{"type":"security_exception","reason":"_opendistro_security_dls_query
    2021-07-25T05:15:12.839052478Z Received an empty response from elasticsearch – server may not be ready
    
  • On the other hand, consecutive jobs are successful as well.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.7
    • 4.8
    • 4.9
  • Red Hat OpenShift Logging Operator
    • 5.0
    • 5.1
    • 5.2

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