Skip to content

Commit fc686fb

Browse files
committed
[DOCS] Fixes build issue in upgrade.asciidoc
1 parent 0019e75 commit fc686fb

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

docs/reference/release-notes/6.3.asciidoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
[[release-notes-6.3.0]]
22
== {es} version 6.3.0
33

4-
=== Known Issues
4+
[float]
5+
=== Known issues
56

67
Clusters with a Gold or Platinum license that are upgrading to 6.3 will need to explicitly set
78
`xpack.security.enabled: true` in `elasticsearch.yml` to upgrade successfully.

docs/reference/upgrade.asciidoc

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
[[setup-upgrade]]
22
= Upgrade Elasticsearch
33

4+
[partintro]
5+
--
46
[IMPORTANT]
5-
7+
===========================================
68
Clusters with a Gold or Platinum license that are upgrading to 6.3 will need to explicitly set
79
`xpack.security.enabled: true` in `elasticsearch.yml` to upgrade successfully.
810
If this value is not set, the cluster will be unable to form after upgrade.
11+
===========================================
912

10-
[partintro]
11-
--
1213
Elasticsearch can usually be upgraded using a <<rolling-upgrades,Rolling upgrade>>
1314
process so upgrading does not interrupt service. However, you might
1415
need to <<reindex-upgrade,Reindex to upgrade>> indices created in older versions.

0 commit comments

Comments
 (0)