# "Resource was created with older version of operator, will not take action" cause ES cluster pods to stuck

**URL:** <https://discuss.elastic.co/t/resource-was-created-with-older-version-of-operator-will-not-take-action-cause-es-cluster-pods-to-stuck/197381>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [August 29, 2019, 4:45pm UTC](https://discuss.elastic.co/t/resource-was-created-with-older-version-of-operator-will-not-take-action-cause-es-cluster-pods-to-stuck/197381 "2019-08-29T16:45:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarjeet](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sarjeet](https://discuss.elastic.co/u/sarjeet)\
**Post date:** [August 29, 2019, 4:45pm UTC](https://discuss.elastic.co/t/resource-was-created-with-older-version-of-operator-will-not-take-action-cause-es-cluster-pods-to-stuck/197381/1 "2019-08-29T16:45:34Z")

</div>

I am facing an issue with the Elasticsearch (w/o kibana or apm) cluster deployment with the custom operator image compiled and built locally (using latest master without any changes) and tried to deploy a simple Elasticsearch yaml, the statefulset pod is stuck in the Init:1/2 state.

I am seeing the following in the operator log which might be the issue here:

{"level":"info","ts":1567096658.9352784,"logger":"annotation","msg":"Resource was created with older version of operator, will not take action","controller\_version":"0.0.0","resource\_controller\_version":"0.0.0","namespace":"default","name":"quickstart"}

Here is the kubectl output for the pod:  
`default quickstart-es-test-0 0/1 Init:1/2 0 4m51s 172.17.0.6 minikube <none> <none>`

The `version: 7.3.0` is specified in the elasticsearch yaml and using following operaor image: sarjesingh/eck-operator:0.10.0-SNAPSHOT-d07c6f08

Please let me know if you'd need me to debug into something to see the issue.

Note: I am able to deploy elasticsearch cluster fine from the quickstart guide.

---

<div class="post-metadata">

**Author:** ![sarjeet](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sarjeet](https://discuss.elastic.co/u/sarjeet)\
**Post date:** [August 29, 2019, 6:04pm UTC](https://discuss.elastic.co/t/resource-was-created-with-older-version-of-operator-will-not-take-action-cause-es-cluster-pods-to-stuck/197381/2 "2019-08-29T18:04:49Z")

</div>

The weird thing is that when reverted operator image back to `docker.elastic.co/eck/eck-operator:0.9.0` and re-created elastic cluster, it works fine.

Not sure how custom image could create the container stuck with the controller/resource version mismatch unless I am missing some information from elasticsearch yaml itself.

---

<div class="post-metadata">

**Author:** ![sarjeet](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sarjeet](https://discuss.elastic.co/u/sarjeet)\
**Post date:** [August 29, 2019, 7:01pm UTC](https://discuss.elastic.co/t/resource-was-created-with-older-version-of-operator-will-not-take-action-cause-es-cluster-pods-to-stuck/197381/3 "2019-08-29T19:01:30Z")

</div>

Filed issue [https://github.com/elastic/cloud-on-k8s/issues/1666](https://github.com/elastic/cloud-on-k8s/issues/1666)

---

<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:** [November 4, 2022, 7:23am UTC](https://discuss.elastic.co/t/resource-was-created-with-older-version-of-operator-will-not-take-action-cause-es-cluster-pods-to-stuck/197381/4 "2022-11-04T07:23:26Z")

</div>