Skip to content

[9.3] [index lifecycle management] Cloned managed ilm policies shouldn't be marked as managed (#248586)#248726

Merged
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-248586
Jan 12, 2026
Merged

[9.3] [index lifecycle management] Cloned managed ilm policies shouldn't be marked as managed (#248586)#248726
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-248586

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

… marked as managed (elastic#248586)

## Summary

This pr fixes the case where a managed index lifecycle management policy
is duplicated and shows as managed. It will now be unmanaged.

Closes elastic#248524

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 6ea176a)
@kibanamachine kibanamachine merged commit a7a4a70 into elastic:9.3 Jan 12, 2026
17 checks passed
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #79 / Alerting mutedAlerts should set ALERT_MUTED field to true for all alerts when muteAll is called
  • [job] [logs] FTR Configs #30 / discover/tabs discover - ES|QL controls should add an ES|QL multi - value control

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
indexLifecycleManagement 146.0KB 146.0KB +70.0B

cc @mattkime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

3 participants