search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.76k stars 8.16k forks source link

Rollover alias is not mandatory when assigning ILM policy to template #105423

Open jsanz opened 3 years ago

jsanz commented 3 years ago

Kibana version: 7.10.0-SNAPSHOT

Browser version: Version 1.26.74 Chromium: 91.0.4472.124 (Official Build) (64-bit)

Browser OS version: Ubuntu 20.04

Original install method (e.g. download page, yum, from source, etc.): Staging cloud

Describe the bug: When an ILM policy includes a rollover action, assigning it to an index template includes the index.lifecycle.rollover_alias setting, which is mandatory according to docs. The UI does not enforce or validate this field.

Steps to reproduce:

  1. Create a ILM policy that includes a rollover (it's included by default in the hot phase)
  2. Assign to an index template
  3. The Alias for rollover index field is not mandatory, so you can add the policy to the template without it (first clip)
  4. Later when the rollover action triggers it fails (second screenshot).

Expected behavior:

This field should be completed with a valid alias name or the policy will fail later when it's triggered.

Screenshots (if relevant):

Peek 2021-07-13 14-04

image

elasticmachine commented 3 years ago

Pinging @elastic/kibana-stack-management (Team:Stack Management)

elasticmachine commented 2 weeks ago

Pinging @elastic/kibana-management (Team:Kibana Management)