# Moving Nodes Updates in 2.4.3 **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [December 17, 2019, 11:53pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240 "2019-12-17T23:53:24Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [December 17, 2019, 11:53pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/1 "2019-12-17T23:53:25Z")
From the 2.4.3 ECE release note: - Moving nodes off allocators for the system-owned deployments `admin-console-elasticsearch` and `logging-and-metrics` now works as expected. I've been trying to move Kibana, the one from `logging-and-metrics` from the existing allocators to the new ones, but I can't do it. Even though, I specify the new target location, I'm failing to move off Kibana. I moved all other nodes (10-15 nodes), but not Kibana node. ---
**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:** [December 18, 2019, 1:27pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/2 "2019-12-18T13:27:22Z")
Interesting! How does the move fail? Alex ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [December 18, 2019, 5:52pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/3 "2019-12-18T17:52:43Z")
I can't move off Kibana from the older allocator to the new ones. There is a spinning wheel next to the deployment after I initiate the action, but it won't complete. There is no errors. ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [December 18, 2019, 7:33pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/4 "2019-12-18T19:33:26Z")
I tried again a few times, but I can't move kibanas off for the last two deployments. One of them is `logging-and-metrics` and the other one is a custom deployment. It just bounces between 3 allocators on which I don't want to have Kibanas on. ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [December 18, 2019, 7:36pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/5 "2019-12-18T19:36:15Z")
I think I found it, the issue might be related to templates/tagging for the kibana instances I had deployed previously. ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [December 18, 2019, 7:40pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/6 "2019-12-18T19:40:49Z")
Yep, it's fixed now. The issue was related to the Kibana templates and tags. The new nodes didn't have appropriate tags. ---
**Author:** ![Jugsofbeer](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@Jugsofbeer](https://discuss.elastic.co/u/Jugsofbeer)\ **Post date:** [December 18, 2019, 9:54pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/7 "2019-12-18T21:54:23Z")
Daniel, You said that there were no errors initially, did you find an error message eventually or did you just figure out it was probably tag related ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 1, 2020, 9:54pm UTC](https://discuss.elastic.co/t/moving-nodes-updates-in-2-4-3/212240/8 "2020-01-01T21:54:24Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.