ILM "Do not modify allocation configuration" default option gives incorrect guidance if allocation was originally "Off" #81697
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:ILM
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Comments
cjcenizal
added
bug
|
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
jloleysens
added a commit
to jloleysens/kibana
that referenced
this issue
Oct 27, 2020
This was referenced Oct 27, 2020
jloleysens
added a commit
that referenced
this issue
Oct 28, 2020
* use form lib fields and start updating deserializer * delete legacy data tier allocation field * finished deserialization * delete legacy serialization, validation and deserialization * fix type issue and remove propertyOf for now * fix legacy tests and create another number validator * added serialization test coverage * fix #81697 * clean up remaining legacy tests and slight update to existing test * remove legacy unused components * fix copy to be clearer for more scenarios * remove remaining coldphase interface use and clean up unused i18n * update default index priority for cold phase * updated cold phase index priority to 0 Co-authored-by: Kibana Machine <[email protected]>
jloleysens
added a commit
to jloleysens/kibana
that referenced
this issue
Oct 28, 2020
* use form lib fields and start updating deserializer * delete legacy data tier allocation field * finished deserialization * delete legacy serialization, validation and deserialization * fix type issue and remove propertyOf for now * fix legacy tests and create another number validator * added serialization test coverage * fix elastic#81697 * clean up remaining legacy tests and slight update to existing test * remove legacy unused components * fix copy to be clearer for more scenarios * remove remaining coldphase interface use and clean up unused i18n * update default index priority for cold phase * updated cold phase index priority to 0 Co-authored-by: Kibana Machine <[email protected]>
jloleysens
added a commit
that referenced
this issue
Oct 29, 2020
* use form lib fields and start updating deserializer * delete legacy data tier allocation field * finished deserialization * delete legacy serialization, validation and deserialization * fix type issue and remove propertyOf for now * fix legacy tests and create another number validator * added serialization test coverage * fix #81697 * clean up remaining legacy tests and slight update to existing test * remove legacy unused components * fix copy to be clearer for more scenarios * remove remaining coldphase interface use and clean up unused i18n * update default index priority for cold phase * updated cold phase index priority to 0 Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: This occurs on master, not on 7.10. 7.10 exhibits a different broken behavior: #81648
To reproduce this bug, save a policy with allocation set to "Off". Edit the policy, change allocation to "Custom", select the default option that states "Do not modify allocation configuration", and save it as in the below screenshot.
Edit it again. Given that the default selected option indicates that the configuration won't be altered, I'd expect allocation to have remained "Off". However, it will be set to "Use cold nodes".
The text was updated successfully, but these errors were encountered: