Backport elastic#111014 to 8.14

thecoop · Jul 18, 2024 · cb14af3 · cb14af3
1 parent e1639e5
commit cb14af3
Show file tree

Hide file tree

Showing 11 changed files with 51 additions and 24 deletions.
diff --git a/docs/reference/release-notes/8.12.0.asciidoc b/docs/reference/release-notes/8.12.0.asciidoc
@@ -14,6 +14,13 @@ there are deleted documents in the segments, quantiles may fail to build and pre
 
 This issue is fixed in 8.12.1.
 
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
+information about the new functionality of these upgraded nodes may not be registered properly with the master node.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
+If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
+To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
+are upgraded. This issue is fixed in 8.15.0.
+
 [[breaking-8.12.0]]
 [float]
 === Breaking changes

diff --git a/docs/reference/release-notes/8.12.1.asciidoc b/docs/reference/release-notes/8.12.1.asciidoc
@@ -3,6 +3,16 @@
 
 Also see <<breaking-changes-8.12,Breaking changes in 8.12>>.
 
+[[known-issues-8.12.1]]
+[float]
+=== Known issues
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
+information about the new functionality of these upgraded nodes may not be registered properly with the master node.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
+If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
+To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
+are upgraded. This issue is fixed in 8.15.0.
+
 [[bug-8.12.1]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.12.2.asciidoc b/docs/reference/release-notes/8.12.2.asciidoc
@@ -3,6 +3,16 @@
 
 Also see <<breaking-changes-8.12,Breaking changes in 8.12>>.
 
+[[known-issues-8.12.2]]
+[float]
+=== Known issues
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
+information about the new functionality of these upgraded nodes may not be registered properly with the master node.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
+If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
+To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
+are upgraded. This issue is fixed in 8.15.0.
+
 [[bug-8.12.2]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.13.0.asciidoc b/docs/reference/release-notes/8.13.0.asciidoc
@@ -21,12 +21,12 @@ This affects clusters running version 8.10 or later, with an active downsampling
 https://www.elastic.co/guide/en/elasticsearch/reference/current/downsampling-ilm.html[configuration]
 or a configuration that was activated at some point since upgrading to version 8.10 or later.
 
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[breaking-8.13.0]]
 [float]

diff --git a/docs/reference/release-notes/8.13.1.asciidoc b/docs/reference/release-notes/8.13.1.asciidoc
@@ -6,12 +6,12 @@ Also see <<breaking-changes-8.13,Breaking changes in 8.13>>.
 [[known-issues-8.13.1]]
 [float]
 === Known issues
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[bug-8.13.1]]
 [float]

diff --git a/docs/reference/release-notes/8.13.2.asciidoc b/docs/reference/release-notes/8.13.2.asciidoc
@@ -6,12 +6,12 @@ Also see <<breaking-changes-8.13,Breaking changes in 8.13>>.
 [[known-issues-8.13.2]]
 [float]
 === Known issues
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[bug-8.13.2]]
 [float]

diff --git a/docs/reference/release-notes/8.13.3.asciidoc b/docs/reference/release-notes/8.13.3.asciidoc
@@ -13,12 +13,12 @@ SQL::
 [[known-issues-8.13.3]]
 [float]
 === Known issues
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[bug-8.13.3]]
 [float]

diff --git a/docs/reference/release-notes/8.13.4.asciidoc b/docs/reference/release-notes/8.13.4.asciidoc
@@ -6,12 +6,12 @@ Also see <<breaking-changes-8.13,Breaking changes in 8.13>>.
 [[known-issues-8.13.4]]
 [float]
 === Known issues
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[bug-8.13.4]]
 [float]

diff --git a/docs/reference/release-notes/8.14.0.asciidoc b/docs/reference/release-notes/8.14.0.asciidoc
@@ -13,12 +13,12 @@ Also see <<breaking-changes-8.14,Breaking changes in 8.14>>.
   The workaround is to grant Elasticsearch read access to the directory mentioned in the `java.nio.file.AccessDeniedException` as observed in the logs
   and repeat this until the process starts up properly, see https://support.elastic.co/knowledge/5979309d[here] for further details.
   With 8.14.1 the workaround won't be necessary anymore and original permissions can be restored.
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
   information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-  This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+  This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
   If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
   To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-  are upgraded.
+  are upgraded. This issue is fixed in 8.15.0.
 
 [[breaking-8.14.0]]
 [float]

diff --git a/docs/reference/release-notes/8.14.1.asciidoc b/docs/reference/release-notes/8.14.1.asciidoc
@@ -7,12 +7,12 @@ Also see <<breaking-changes-8.14,Breaking changes in 8.14>>.
 [[known-issues-8.14.1]]
 [float]
 === Known issues
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[bug-8.14.1]]
 [float]

diff --git a/docs/reference/release-notes/8.14.2.asciidoc b/docs/reference/release-notes/8.14.2.asciidoc
@@ -6,12 +6,12 @@ Also see <<breaking-changes-8.14,Breaking changes in 8.14>>.
 [[known-issues-8.14.2]]
 [float]
 === Known issues
-* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
+* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
 information about the new functionality of these upgraded nodes may not be registered properly with the master node.
-This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
+This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
 If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
 To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
-are upgraded.
+are upgraded. This issue is fixed in 8.15.0.
 
 [[bug-8.14.2]]
 [float]