github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS+] Add #158940 to the list of 8.8.0 known issues (#159197)

Browse source 
This PR adds https://github.com/elastic/kibana/issues/158733 to the list
of known issues:
* issue: https://github.com/elastic/kibana/issues/158733
* pull: https://github.com/elastic/kibana/pull/158940

---------

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
This commit is contained in:
Gerard Soldevila 2023-06-07 15:16:53 +02:00 • committed by GitHub
parent 346d54c33e
commit 528671e3bd
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/CHANGELOG.asciidoc
View file

@ -51,6 +51,21 @@ Review the following information about the {kib} 8.8.0 release.
[[known-issues-8.8.0]]
=== Known issues
// tag::known-issue-158940[]
[discrete]
.Failed upgrades to 8.8.0 can cause bootlooping and data loss
[%collapsible]
====
*Details* +
The 8.8.0 release splits the `.kibana` index into multiple saved object indices. If an upgrade to 8.8.0 partially succeeds, but not all the indices are created successfully, {kib} may be unable to successfully complete the upgrade on the next restart.
This can result in a loss of saved objects during the upgrade. This can also leave {kib} in a bootlooping state where it's unable to start due to `write_blocked` indices.
*Impact* +
The 8.8.1 release includes in {kibana-pull}158940[a fix] for this problem. Customers affected by a failed 8.8.0 upgrade should contact Elastic support. For more information, see the {kibana-issue}58733[related issue].
====
// end::known-issue-158940[]
// tag::known-issue-155203[]
[discrete]
.Monitors in Synthetics may stop running