Add known-issue docs for elastic#92812 (elastic#92813)

abdonpijpelink · Jan 11, 2023 · bb37dc2 · bb37dc2
1 parent 4c6efcc
commit bb37dc2
Show file tree

Hide file tree

Showing 9 changed files with 46 additions and 20 deletions.
diff --git a/docs/reference/release-notes/8.4.0.asciidoc b/docs/reference/release-notes/8.4.0.asciidoc
@@ -13,13 +13,21 @@ Also see <<breaking-changes-8.4,Breaking changes in 8.4>>.
 If you have a {dfeed} that was created in version 5.x or 6.x and has not
 been updated since 7.0, it is not possible to list {dfeeds} in 
 8.4 and 8.5. This means that {anomaly-jobs} cannot be managed using
-{kib}. This issue is fixed in 8.6.
+{kib}. This issue is fixed in 8.6.0.
 +
 If you upgrade to 8.4 or 8.5 with such a {dfeed}, you need to
 work around the problem by updating each {dfeed}'s authorization information
 using https://support.elastic.dev/knowledge/view/b5a879db[these steps].
 // end::ml-pre-7-datafeeds-known-issue[]
 
+// tag::file-based-settings-deadlock-known-issue[]
+* Orchestrators which use a `settings.json` file to configure Elasticsearch may
+encounter deadlocks during master elections (issue: {es-issue}92812[#92812])
++
+To resolve the deadlock, remove the `settings.json` file and restart the
+affected node.
+// end::file-based-settings-deadlock-known-issue[]
+
 [[bug-8.4.0]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.4.1.asciidoc b/docs/reference/release-notes/8.4.1.asciidoc
@@ -3,14 +3,6 @@
 
 Also see <<breaking-changes-8.4,Breaking changes in 8.4>>.
 
-[[bug-8.4.1]]
-[float]
-=== Bug fixes
-
-Machine Learning::
-* [ML] Validate trained model deployment `queue_capacity` limit {es-pull}89611[#89611] (issue: {es-issue}89555[#89555])
-
-
 [[known-issues-8.4.1]]
 [float]
 === Known issues
@@ -20,3 +12,12 @@ an incorrectly parsed date could be used. The workaround is to use date pattern
 (issue: {es-issue}90187[#90187])
 
 include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
+
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
+[[bug-8.4.1]]
+[float]
+=== Bug fixes
+
+Machine Learning::
+* [ML] Validate trained model deployment `queue_capacity` limit {es-pull}89611[#89611] (issue: {es-issue}89555[#89555])
diff --git a/docs/reference/release-notes/8.4.2.asciidoc b/docs/reference/release-notes/8.4.2.asciidoc
@@ -22,6 +22,8 @@ an incorrectly parsed date could be used. The workaround is to use date pattern
 
 include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
 
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[bug-8.4.2]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.4.3.asciidoc b/docs/reference/release-notes/8.4.3.asciidoc
@@ -3,6 +3,18 @@
 
 Also see <<breaking-changes-8.4,Breaking changes in 8.4>>.
 
+[[known-issues-8.4.3]]
+[float]
+=== Known issues
+
+* When using date range search with format that does not have all date fields (missing month or day)
+an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
+(issue: {es-issue}90187[#90187])
+
+include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
+
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[bug-8.4.3]]
 [float]
 === Bug fixes
@@ -19,14 +31,3 @@ Ingest Node::
 
 Ranking::
 * Ensure `cross_fields` always uses valid term statistics {es-pull}90314[#90314]
-
-
-[[known-issues-8.4.3]]
-[float]
-=== Known issues
-
-* When using date range search with format that does not have all date fields (missing month or day)
-an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
-(issue: {es-issue}90187[#90187])
-
-include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
diff --git a/docs/reference/release-notes/8.5.0.asciidoc b/docs/reference/release-notes/8.5.0.asciidoc
@@ -16,6 +16,8 @@ affected by this issue, upgrade to 8.5.3 to repair it ({es-pull}91887[#91887]).
 
 include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
 
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[breaking-8.5.0]]
 [float]
 === Breaking changes

diff --git a/docs/reference/release-notes/8.5.1.asciidoc b/docs/reference/release-notes/8.5.1.asciidoc
@@ -10,6 +10,8 @@ Also see <<breaking-changes-8.5,Breaking changes in 8.5>>.
 
 include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
 
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[bug-8.5.1]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.5.2.asciidoc b/docs/reference/release-notes/8.5.2.asciidoc
@@ -10,6 +10,8 @@ Also see <<breaking-changes-8.5,Breaking changes in 8.5>>.
 
 include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
 
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[bug-8.5.2]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.5.3.asciidoc b/docs/reference/release-notes/8.5.3.asciidoc
@@ -9,6 +9,8 @@ Also see <<breaking-changes-8.5,Breaking changes in 8.5>>.
 
 include::8.4.0.asciidoc[tag=ml-pre-7-datafeeds-known-issue]
 
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[bug-8.5.3]]
 [float]
 === Bug fixes

diff --git a/docs/reference/release-notes/8.6.0.asciidoc b/docs/reference/release-notes/8.6.0.asciidoc
@@ -3,6 +3,12 @@
 
 Also see <<breaking-changes-8.6,Breaking changes in 8.6>>.
 
+[[known-issues-8.6.0]]
+[float]
+=== Known issues
+
+include::8.4.0.asciidoc[tag=file-based-settings-deadlock-known-issue]
+
 [[bug-8.6.0]]
 [float]
 === Bug fixes