Elasticsearch deployments are not created after deploying clusterlogging instance

Solution Verified - Updated -

Issue

  • After deployment of elasticsearch and clusterlogging operators, while creating clusterlogging instance, the elasticsearch deployments and pods are not created.
# oc get deployment
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
cluster-logging-operator   1/1     1            1           27h
kibana                     1/1     1            1           27h
# oc get pods
NAME                                        READY   STATUS    RESTARTS   AGE
cluster-logging-operator-xxxx-xxxx   1/1     Running   0          4h35m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
fluentd-xxxxx                               1/1     Running   0          5h7m
kibana-xxxx-xxxx                     2/2     Running   0          5h7m

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.4

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