From 850c266a3af12f417d2b5275b58311e6533a95d6 Mon Sep 17 00:00:00 2001 From: Gerard Soldevila Date: Wed, 7 Jun 2023 13:22:26 +0200 Subject: [PATCH 1/3] Add 158940 to the list of known issues --- docs/CHANGELOG.asciidoc | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/CHANGELOG.asciidoc b/docs/CHANGELOG.asciidoc index fe9a58602a339..b70b8a491cc65 100644 --- a/docs/CHANGELOG.asciidoc +++ b/docs/CHANGELOG.asciidoc @@ -77,6 +77,18 @@ With network throttling being disabled, your monitors may run more quickly (i.e. ==== // end::known-issue-156798[] +// tag::known-issue-158940[] +[discrete] +.Failed upgrades to 8.8.0 could cause bootlooping and possibly data loss during upgrade +==== +*Details* + +The 8.8.0 release splits the `.kibana` index into multiple saved object indices. If the upgrade partially succeeds, but not all the indices are created successfully, Kibana might be unable to successfully complete the upgrade on the next restart. Whilst 8.8.1 release includes in {kibana-pull}a fix[#158940] for this problem, customers affected by a failed 8.8.0 upgrade should refer to the https://github.com/elastic/kibana/issues/158733[related issue] for more information, and eventually contact support. + +*Impact* + +Eventually, some of the saved objects that should be dispatched to the newer indices may be lost during the upgrade. Kibana can also be left on a bootlooping state where it is no longer able to start, due to `write_blocked` indices. +==== +// end::known-issue-158940[] + [float] [[breaking-changes-8.8.0]] === Breaking changes From 0806adcac9e76fc315ce3af97acc5b6009893317 Mon Sep 17 00:00:00 2001 From: Gerard Soldevila Date: Wed, 7 Jun 2023 14:42:47 +0200 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: James Rodewig --- docs/CHANGELOG.asciidoc | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/CHANGELOG.asciidoc b/docs/CHANGELOG.asciidoc index b70b8a491cc65..2f424910b7350 100644 --- a/docs/CHANGELOG.asciidoc +++ b/docs/CHANGELOG.asciidoc @@ -79,13 +79,16 @@ With network throttling being disabled, your monitors may run more quickly (i.e. // tag::known-issue-158940[] [discrete] -.Failed upgrades to 8.8.0 could cause bootlooping and possibly data loss during upgrade +.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 the upgrade partially succeeds, but not all the indices are created successfully, Kibana might be unable to successfully complete the upgrade on the next restart. Whilst 8.8.1 release includes in {kibana-pull}a fix[#158940] for this problem, customers affected by a failed 8.8.0 upgrade should refer to the https://github.com/elastic/kibana/issues/158733[related issue] for more information, and eventually contact support. +he 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* + -Eventually, some of the saved objects that should be dispatched to the newer indices may be lost during the upgrade. Kibana can also be left on a bootlooping state where it is no longer able to start, due to `write_blocked` indices. +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[] From 7ce9b935fd77df4f0867e1129a2e390660793b35 Mon Sep 17 00:00:00 2001 From: Gerard Soldevila Date: Wed, 7 Jun 2023 14:45:41 +0200 Subject: [PATCH 3/3] Put 158940 on top of the Known Issues --- docs/CHANGELOG.asciidoc | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/CHANGELOG.asciidoc b/docs/CHANGELOG.asciidoc index 2f424910b7350..a7a665d9c40ce 100644 --- a/docs/CHANGELOG.asciidoc +++ b/docs/CHANGELOG.asciidoc @@ -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 @@ -77,21 +92,6 @@ With network throttling being disabled, your monitors may run more quickly (i.e. ==== // end::known-issue-156798[] -// tag::known-issue-158940[] -[discrete] -.Failed upgrades to 8.8.0 can cause bootlooping and data loss -[%collapsible] -==== -*Details* + -he 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[] - [float] [[breaking-changes-8.8.0]] === Breaking changes