Hi Team,
I have this index as part of datastream which is still in HOT phase , with current step as ERROR
{
"failed_step": "update-rollover-lifecycle-date",
"step_info": {
"type": "illegal_state_exception",
"reason": "no rollover info found for [.ds-abc-2025.05.25-000004] with rollover target [traces-abc-maint], the index has not yet rolled over with that target"
}
}
This index do have a policy tagged & the indices are rolled over everyday 1D or 50GB size.
There are new indices created post 25 successfully. This index is stuck.
What actions could be taken so that this follow the policy and moves from HOT Phase to next Phase (WARM node) ?
Thanks
Your situation look like this:
ILM Error: the index has not yet rolled over with that target : r/elasticsearch
The reddit post also link to Elastic Github:
Rollover sometimes does not attach Rollover Info to index metadata · Issue #49413 · elastic/elasticsearch
In a nutshell:
From what I understand your index may or may not have a RolloverInfo
and a workaround as well:
POST _ilm/move/cloudflare-2022.07.14-000001
{
"current_step": {
"phase": "hot",
"action": "rollover",
"name": "ERROR"
},
"next_step": {
"phase": "hot",
"action": "rollover",
"name": "set-indexing-complete"
}
}
You should try it, and hope you let me know the result 
Thanks @NgDinhNamEtiis for sharing the details. I will review and let you know if the issue get fixed.