# Resolving 'Freezing deprecated' migration assistant warnings

**URL:** <https://discuss.elastic.co/t/resolving-freezing-deprecated-migration-assistant-warnings/374285>\
**Category:** Elasticsearch\
**Tags:** migration\
**Created:** [February 10, 2025, 1:21am UTC](https://discuss.elastic.co/t/resolving-freezing-deprecated-migration-assistant-warnings/374285 "2025-02-10T01:21:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DPattee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpattee/32/37772_2.png) [@DPattee](https://discuss.elastic.co/u/DPattee)\
**Post date:** [February 10, 2025, 1:21am UTC](https://discuss.elastic.co/t/resolving-freezing-deprecated-migration-assistant-warnings/374285/1 "2025-02-10T01:21:56Z")

</div>

I've resolved all the critical Upgrade Assistant issues in prep for a 7.17 -\> 8 upgrade, including removing 'freeze' steps from my ILM policies. But there are nearly 150 "Freezing indices is deprecated" warnings left.

My current understanding is that for each index I could use the rest api to \_unfreeze, and then push a blob with a read only attribute, and then another to move the index to cold storage.

That's 450 curls... Obviously this could be done in a script, but am I missing something? Is there some 'fix it' button somewhere that I haven't noticed in Kibana? Or will that automatically happen once the cluster is brought up to v8 on all nodes?