# Restore 6.1.1 to 7.3.1 bug?

**URL:** <https://discuss.elastic.co/t/restore-6-1-1-to-7-3-1-bug/204288>\
**Category:** Elasticsearch\
**Created:** [October 18, 2019, 11:26pm UTC](https://discuss.elastic.co/t/restore-6-1-1-to-7-3-1-bug/204288 "2019-10-18T23:26:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [October 18, 2019, 11:26pm UTC](https://discuss.elastic.co/t/restore-6-1-1-to-7-3-1-bug/204288/1 "2019-10-18T23:26:31Z")

</div>

Is this a known issue?  
I was running 7.3.0 and restored ran fine.  
But now upgraded to 7.3.1, I'm getting unassigned shards.

---

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [October 18, 2019, 11:34pm UTC](https://discuss.elastic.co/t/restore-6-1-1-to-7-3-1-bug/204288/2 "2019-10-18T23:34:46Z")

</div>

Hmm. I think the problem is not all the nodes have s3 plugins.

---

<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 15, 2019, 11:34pm UTC](https://discuss.elastic.co/t/restore-6-1-1-to-7-3-1-bug/204288/3 "2019-11-15T23:34:48Z")

</div>

Closed on November 15, 2019, 11:34pm UTC

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