# Single master node stuck on the wrong AZ and will not move

**URL:** <https://discuss.elastic.co/t/single-master-node-stuck-on-the-wrong-az-and-will-not-move/239812>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [July 3, 2020, 1:30pm UTC](https://discuss.elastic.co/t/single-master-node-stuck-on-the-wrong-az-and-will-not-move/239812 "2020-07-03T13:30:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\
**Post date:** [July 3, 2020, 1:30pm UTC](https://discuss.elastic.co/t/single-master-node-stuck-on-the-wrong-az-and-will-not-move/239812/1 "2020-07-03T13:30:34Z")

</div>

I've been able to get all of my lab environment nodes to upgrade from 7.5.1 to 7.8.0 except for a single master node that got allocated onto transitional Allocator, one that isn't designated hot warm or frozen and now it wont move off of that Allocator. When I try to move it to the proper AZ I get the error below. It seems like if I use the failover.force=true it will allow this master node to move off of the Allocator. Overall trying to upgrade the deployment and move this node have failed every time.

````auto

[validate-plan-prerequisites]: [no.found.constructor.validation.ValidationException: 1. Unsupported downgrade attempted from [List(7.5.1, 7.8.0, 7.8.0, 7.8.0, 7.8.0, 7.8.0, 7.8.0, 7.5.1, 7.8.0, 7.8.0, 7.8.0, 7.5.1, 7.8.0, 7.5.1, 7.8.0)] to [7.5.1]. You can override this check with failover.force=true]"```
````

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [July 6, 2020, 2:22pm UTC](https://discuss.elastic.co/t/single-master-node-stuck-on-the-wrong-az-and-will-not-move/239812/2 "2020-07-06T14:22:51Z")

</div>

How are you moving it? Using the "Move" UI element for a single node should result in the flag `move_only` being set (you can see in the "Details" section of the "Activity" page), which should avoid that error

If it isn't setting that flag (maybe if you're running an older ECE?), then I would apply the `move_instances` by hand and set `move_only` at the same time, via the advanced editor)

(The error itself is because you are declaring that you want the end state of the cluster to be 7.5.1 but it already has 7.8.0 nodes in it - the other option would be to manually up the `version` to 7.8.0 in the advanced plan editor, together with the `move_instances` ... that would have the advantage of fixing your cluster at the same time, but `move_only` is the quickest way of getting your node off the allocator in question)

---

<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:** [July 20, 2020, 2:22pm UTC](https://discuss.elastic.co/t/single-master-node-stuck-on-the-wrong-az-and-will-not-move/239812/3 "2020-07-20T14:22:52Z")

</div>

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