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.

Sign up for GitHub

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

Jump to bottom

[docs] Document how to solve migrations failing with unknown saved object types #119944

Closed
rudolf opened this issue Nov 30, 2021 · 1 comment
Closed

[docs] Document how to solve migrations failing with unknown saved object types #119944

rudolf opened this issue Nov 30, 2021 · 1 comment
Labels
docs impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0

Comments

@rudolf
Copy link
Contributor

rudolf commented Nov 30, 2021

Starting in 8.0 Kibana will refuse to start if there are unknown saved object types present in the saved object indices #107678

We are informing users by logging a warning every time kibana starts on 7.16+ and surfacing this warning in the upgrade assistant. However, it would still be useful to explain this warning in more detail in https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#preventing-migration-failures
@rudolf rudolf added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0 docs labels Nov 30, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@exalate-issue-sync exalate-issue-sync bot added impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:small Small Level of Effort impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. and removed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. labels Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rudolf @elasticmachine