Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana Edit index lifecycle policy GUI doesn't allow 0 for delete phase timing #55768

Closed
Nick-Anderssohn opened this issue Jan 24, 2020 · 2 comments
Labels
Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@Nick-Anderssohn
Copy link

Kibana version: 7.4.1

Elasticsearch version: 7.4.1

Server OS version: linux/amd64

Browser version: Chrome

Browser OS version: linux/amd64

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

Describe the bug: The gui for editing an index lifecycle policy doesn't allow you to set min_age of the delete phase to 0. Instead it displays an error. The error message appears to be caused by client-side validation rather than an error being returned from ElasticSearch.

Steps to reproduce:

  1. Create an ILM policy.
  2. Go to Management -> Index Lifecycle Policies and select the policy.
  3. Enable the delete phase if it isn't already.
  4. Try to save 0 as the value for "Timing for delete phase".
  5. A red line will appear under the box, and hovering over the input box will display this error message: "Value must be greater than or equal to 1."

Expected behavior:
It allows you to save the policy.

Screenshots (if relevant):
delete_phase_min_age

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@azasypkin azasypkin added Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Jan 24, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@cjcenizal
Copy link
Contributor

Thanks for reporting this @Nick-Anderssohn! I believe this is a duplicate of #50476. If so, then we've fixed this bug via #53719. The fix will ship with 7.6.0.

I'm going to close this but if you believe this is a different bug we'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

4 participants