# Unable to upgrade System owned cluster from 6.6.1 to 6.7.1

**URL:** <https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925>\
**Category:** Elasticsearch\
**Created:** [May 14, 2019, 6:27am UTC](https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925 "2019-05-14T06:27:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jude\_Jerome](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jude_jerome/32/46122_2.png) [@Jude\_Jerome](https://discuss.elastic.co/u/Jude_Jerome)\
**Post date:** [May 14, 2019, 6:27am UTC](https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925/1 "2019-05-14T06:27:09Z")

</div>

Hello Together,

I am trying to upgrade my System owned cluster from 6.6.1 to 6.7.1 and while upgrading

Stopping Index Lifecycle Management steps makes more time and it is failed with below error

Error:

- Starting step: [stop-ilm]: 

- Operation mode is [STOPPING], waiting for it to transition to [STOPPED]...

- Unexpected error during step: [stop-ilm]: [no.found.constructor.models.TimeoutException: Timeout]

I have tried to stop the ilm and it is still in stopping state.

Any thoughts on this.

---

<div class="post-metadata">

**Author:** ![vjsablok](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vjsablok/32/46124_2.png) [@vjsablok](https://discuss.elastic.co/u/vjsablok)\
**Post date:** [May 14, 2019, 6:31am UTC](https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925/2 "2019-05-14T06:31:00Z")

</div>

Elasticsearch can usually be upgraded using a [Rolling upgrade](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/rolling-upgrades.html) process so upgrading does not interrupt service. However, you might need to [Reindex to upgrade](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/reindex-upgrade.html) indices created in older versions. Upgrades across major versions prior to 6.0 require a [Full cluster restart](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/restart-upgrade.html).

When upgrading to a new version of Elasticsearch, you need to upgrade each of the products in your Elastic Stack. The steps you need to take to upgrade differ depending on which products you are using.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [May 14, 2019, 6:39am UTC](https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925/3 "2019-05-14T06:39:06Z")

</div>

This exception is coming from the Elastic Cloud infrastructure rather than from Elasticsearch itself. Could you open a support ticket about it?

---

<div class="post-metadata">

**Author:** ![Jude\_Jerome](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jude_jerome/32/46122_2.png) [@Jude\_Jerome](https://discuss.elastic.co/u/Jude_Jerome)\
**Post date:** [May 14, 2019, 6:40am UTC](https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925/4 "2019-05-14T06:40:53Z")

</div>

Thanks David. I Will get it touch with support team.

---

<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:** [June 11, 2019, 6:40am UTC](https://discuss.elastic.co/t/unable-to-upgrade-system-owned-cluster-from-6-6-1-to-6-7-1/180925/5 "2019-06-11T06:40:54Z")

</div>

Closed on June 11, 2019, 6:40am UTC

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