# "reset" ILM failed step

**URL:** <https://discuss.elastic.co/t/reset-ilm-failed-step/327754>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security, ilm-index-lifecycle-management\
**Created:** [March 15, 2023, 1:09pm UTC](https://discuss.elastic.co/t/reset-ilm-failed-step/327754 "2023-03-15T13:09:14Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![pestevao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pestevao/32/44138_2.png) [@pestevao](https://discuss.elastic.co/u/pestevao)\
**Post date:** [April 18, 2023, 3:40pm UTC](https://discuss.elastic.co/t/reset-ilm-failed-step/327754/8 "2023-04-18T15:40:44Z")

</div>

Final solution at last!

Have created a new (user) Role with "allow\_restricted\_indices": true permission and "all" on the restricted indice, like this:

```auto
POST /_security/role/_temp_restricted_indice_permission
{
  "indices": [
    {
      "names": [".restricted-indice-name"],
      "privileges": ["all"],
      "allow_restricted_indices": true
    }
  ]
}

```

  
Then go to Kibana -\> Management -\> Users and give this role to your user.

Next go to Kibana -\> Management -\> Index Management, filter by indices with errors, go to detail to each one of the indices and click "Manage ^" -\> "Remove lifecycle policy" like shown bellow:  
  
  
 ![imagem](https://us1.discourse-cdn.com/elastic/original/3X/7/7/77f6e81b4a63acc18314a5ef3473074b1648d7ac.png)  
  
  
Solve this issue, no more indices with errors and no restricted indices or system configuration / information was affected! 🙂

Thank you all for your inputs and shared ideas.

Greetings, Pedro  
  
  
P.S. - maybe just manage\_ilm or manage permissions on (user) Role catching the restricted indice will do the job but...

---

_[View the full topic](https://discuss.elastic.co/t/reset-ilm-failed-step/327754)._