Description of problem:
The rollover- and -delete- pods in cluster-logging instance on OCP4.6 enter Error state. My customer upgraded from OCP4.5.23 to 4.6.8 for this fix. But this Bug did not resolve yet. So I reopened this ticket.

Version-Release number of selected component (if applicable):
OpenShift：4.6.8
Operator Cluster Logging：4.6.0-202011221454

Actual results:

- The log of elasticsearch-delete-infra-********-****
{
  "error" : {
    "root_cause" : [
      {
        "type" : "security_exception",
        "reason" : "Unexpected exception indices:admin/delete"
      }
    ],
    "type" : "security_exception",
    "reason" : "Unexpected exception indices:admin/delete"
  },
  "status" : 500
}

- Part of result from 'oc get pod -n openshift-logging'
NAME                                            READY   STATUS      RESTARTS   AGE
<snip>
curator-**********-*****                        0/1     Error       0          21h
<snip>
elasticsearch-delete-infra-**********-*****     0/1     Error       0          7d12h
<snip>
elasticsearch-rollover-app-**********-*****     0/1     Error       0          37d
<snip>
elasticsearch-rollover-audit-**********-*****   0/1     Error       0          3d10h
<snip>
elasticsearch-rollover-infra-**********-*****   0/1     Error       0          34d

Expected results:

Their Pod run in a normal state.

Additional info:

This bug must be fixed as follows.

RHBA-2020:4198 - Bug Fix Advisory
https://access.redhat.com/errata/RHBA-2020:4198

Bug 1866019 - elasticsearch-rollover and elasticsearch-delete pods in Error states
https://bugzilla.redhat.com/show_bug.cgi?id=1866019