-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Index Management] Provide more info than just "Bad Request" when retrying lifecycle step #118464
Comments
Pinging @elastic/kibana-stack-management (Team:Stack Management) |
@maltewhiite Thanks for creating this issue! To help us understand what's occurring we need more information. Which version are you on? Are there steps that you can share that we can follow to reliably reproduce the error? Thanks. |
Which version of Elastic? Where can I see that? |
I went from changing indices daily to changing to the 000001 method. I opened this discuss.elastic thread about all my ILM issues. It has been a completely new thing to me, so I've had a lot of struggle with it. Never done anything like this before in my career. |
I have had the same issue.
|
@ElenaStoeva do you think this has been resolved by #162656? |
That PR resolved the empty error toast from the index actions but it seems I missed to also fix the error toast from the extension actions (the "Retry lifecycle step" is one of the ILM extension actions) so I opened a small PR with a fix: #173620 |
…ns (#173620) Fixes #118464 Similar to #162656 ## Summary This PR fixes the empty error toast that appears from a failed extension action. For example, when the ILM extension action "Retry lifecycle step" fails, it would display an empty error toast on cloud (or it would display "Bad request" when running locally): https://github.com/elastic/kibana/assets/59341489/37c3113a-4f2b-4157-ab0c-658c410349c8 With these changes, the error toast also displays the message: https://github.com/elastic/kibana/assets/59341489/1f6df5c4-381f-4039-b5f3-746c5783bd2c **How to test:** For testing a failing "Retry lifecycle step" action, I followed the instructions in this [README](https://github.com/elastic/kibana/blob/main/x-pack/plugins/index_lifecycle_management/README.md) file to create a lifecycle policy error. The changes in this PR can be tested in its [CI Cloud deployment](https://kibana-pr-173620.kb.us-west2.gcp.elastic-cloud.com:9243/).
Describe the feature:
Provide more info than just "Bad Request", when trying to "Retry lifecycle step" on indices with lifecycle errors.
I have no idea how to find out what is going wrong, when the only thing I am told is "Bad Request"
Describe a specific use case for the feature:
If a user is having issues figuring out why their ILM is going wrong and are retrying lifecycle steps, and they get "Bad Request", they should be provided more info than that, about what went wrong, so they can try to resolve the problem.
The text was updated successfully, but these errors were encountered: