-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Docs] Add known issue about upgrade error #207629
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
Merged
wajihaparvez
merged 5 commits into
elastic:8.x
from
wajihaparvez:622-upgrade-error-500-known-issue
Jan 23, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c1d30b1
[Docs] Add known issue upgrade error
wajihaparvez ccbbeb3
[Docs] add workaround and copy to other affected versions
wajihaparvez 89c392f
[Docs] edit workaround based on feedback
wajihaparvez 1c79f04
Merge branch '8.x' into 622-upgrade-error-500-known-issue
wajihaparvez 8555b39
fix double ID
florent-leborgne File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not able to propose changes for some reason but here are the steps to mitigate:
This issue can be mitigated by searching the
.kibana_*index fortype: inventory_view, capturing the_idfield,which will hold the format
inventory-view:<id>, e.g.:inventory-view:3d3d06b0-f873-4373-8446-f6a8341cd8b1.The offending documents are those with fields
inventory-view.legend.steps> 18.Then delete those documents using the following in the Dev Tool Console:
Note: the
inventory-view:portion of the _id field is removed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bryce-b! I made a few readability edits and added this in, if you want to have a look at the preview once it rebuilds