Kibana pod from cluster-logging-operator 4.3 is continuosly restarting on Openshift 4.4

Solution Verified - Updated -

Issue

  • Kibana pod from cluster-logging-operator 4.3 is continuously restarting on Openshift 4.4 with the following error:
June 16th 2020, 10:53:57.902    I0616 08:53:57.902139    1386 event.go:281] Event(v1.ObjectReference{Kind:"Pod", Namespace:"openshift-logging", Name:"kibana-6ccf8ff69f-t9bwn", UID:"33c13c4b-6c66-4dbc-9b5e-c94441906a05", APIVersion:"v1", ResourceVersion:"40561317", FieldPath:"spec.containers{kibana}"}): type: 'Warning' reason: 'Unhealthy' Readiness probe errored: rpc error: code = Unknown desc = container is not created or running
June 16th 2020, 10:53:57.901    I0616 08:53:57.901643    1386 event.go:281] Event(v1.ObjectReference{Kind:"Pod", Namespace:"openshift-logging", Name:"kibana-6ccf8ff69f-t9bwn", UID:"33c13c4b-6c66-4dbc-9b5e-c94441906a05", APIVersion:"v1", ResourceVersion:"40561317", FieldPath:"spec.containers{kibana}"}): type: 'Warning' reason: 'Unhealthy' Readiness probe errored: rpc error: code = Unknown desc = container is not created or running

Environment

  • Red Hat Openshift Container Platform (OCP) 4.4
  • Cluster Logging Operator installed from channel 4.3

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