# Elasticsearch stuck in ApplyingChanges phase on Openshift

**URL:** <https://discuss.elastic.co/t/elasticsearch-stuck-in-applyingchanges-phase-on-openshift/323228>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [January 16, 2023, 8:18am UTC](https://discuss.elastic.co/t/elasticsearch-stuck-in-applyingchanges-phase-on-openshift/323228 "2023-01-16T08:18:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TimTim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timtim/32/5295_2.png) [@TimTim](https://discuss.elastic.co/u/TimTim)\
**Post date:** [January 16, 2023, 8:18am UTC](https://discuss.elastic.co/t/elasticsearch-stuck-in-applyingchanges-phase-on-openshift/323228/1 "2023-01-16T08:18:29Z")

</div>

Hi!

We're running Openshift 4.11 and we've installed ECK 2.6.2. I start an Elasticsearch instance with this YAML code (copied from the quickstart doc):

```auto
cat <<EOF | oc apply -n 008ep-elk -f -
# This sample sets up an Elasticsearch cluster with an OpenShift route
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: gbg
spec:
  version: 8.6.0
  nodeSets:
  - name: prod
    count: 1
    config:
      node.store.allow_mmap: false
EOF

```

The pod gets created and is up and running after a while:

```auto
$ oc get pods
NAME READY STATUS RESTARTS AGE
gbg-es-prod-0 1/1 Running 0 17m

```

Even when I go into the pod and check for health status, I get code green. So everything is working there. But the problem is that the status for Elasticsearch (under Operator) is still saying ApplyingChanges:

```auto
$ oc get elasticsearch
NAME HEALTH NODES VERSION PHASE AGE
gbg unknown 1 8.6.0 ApplyingChanges 16m

```

The question is if this has to do with the **Readiness probe** that failed for the elasticsearch pod?

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [January 16, 2023, 3:07pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-in-applyingchanges-phase-on-openshift/323228/2 "2023-01-16T15:07:59Z")

</div>

I've installed ECK 2.6.2 using the operator hub, and then successfully created an Elasticsearch resource using the manifest you provided:

```auto
oc get es,pods
NAME HEALTH NODES VERSION PHASE AGE
elasticsearch.elasticsearch.k8s.elastic.co/gbg green 1 8.6.0 Ready 73s

NAME READY STATUS RESTARTS AGE
pod/gbg-es-prod-0 1/1 Running 0 71s

```

Could you look at the operator's logs to check if there's any error message? Also there may be more information in the Elasticsearch status subresource: `oc get elasticsearch.elasticsearch.k8s.elastic.co/gbg --output=jsonpath='{ .status }'`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 13, 2023, 3:08pm UTC](https://discuss.elastic.co/t/elasticsearch-stuck-in-applyingchanges-phase-on-openshift/323228/3 "2023-02-13T15:08:12Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.