Skip to content

Commit 1cd27e7

Browse files
committed
Docs: Add known issue for removing x-pack
6.4 can no longer remove the x-pack plugin so users must remove it before upgrading to 6.4+. We've already updated the upgrade documentation. This updates the release notes and breaking changes docs. Closes #34307
1 parent a9da8fe commit 1cd27e7

File tree

2 files changed

+20
-1
lines changed

2 files changed

+20
-1
lines changed

docs/reference/migration/migrate_6_4.asciidoc

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,16 @@
77
This section discusses the changes that you need to be aware of when migrating
88
your application to Elasticsearch 6.4.
99

10+
[IMPORTANT]
11+
.bin/plugin can no longer remove x-pack
12+
=========================================
13+
14+
`bin/plugin remove x-pack` no longer works. You should remove the {xpack}
15+
plugin before upgrading to 6.4 or any later versions. More instructions
16+
available in <<rolling-upgrades>> and <<restart-upgrade>>.
17+
18+
=========================================
19+
1020
* <<breaking_64_api_changes>>
1121
* <<breaking_64_scripting_changes>>
1222

docs/reference/release-notes/6.4.asciidoc

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,9 +98,18 @@ Caused by: org.elasticsearch.common.xcontent.XContentParseException: [-1:####] [
9898
9999
======================================================
100100

101+
[IMPORTANT]
102+
.bin/plugin can no longer remove x-pack
103+
=========================================
104+
105+
`bin/plugin remove x-pack` no longer works. You should remove the {xpack}
106+
plugin before upgrading to 6.4 or any later versions.
107+
108+
=========================================
109+
101110
[float]
102111
=== Known issues
103-
See the important section above.
112+
See the important sections above.
104113

105114
{es} 6.4.0 fails to start when PEM encoded private key files that have been exported from `PKCS#12`
106115
keystores are in use. These files can be identified by the existence of lines that start with either

0 commit comments

Comments
 (0)