From 1cd27e72ef5c9db1d3764aabc670b896d1430d47 Mon Sep 17 00:00:00 2001 From: Nik Everett Date: Wed, 17 Oct 2018 09:10:13 -0400 Subject: [PATCH] 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 --- docs/reference/migration/migrate_6_4.asciidoc | 10 ++++++++++ docs/reference/release-notes/6.4.asciidoc | 11 ++++++++++- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/docs/reference/migration/migrate_6_4.asciidoc b/docs/reference/migration/migrate_6_4.asciidoc index 44fa915e365a5..6519352c7e550 100644 --- a/docs/reference/migration/migrate_6_4.asciidoc +++ b/docs/reference/migration/migrate_6_4.asciidoc @@ -7,6 +7,16 @@ This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 6.4. +[IMPORTANT] +.bin/plugin can no longer remove x-pack +========================================= + +`bin/plugin remove x-pack` no longer works. You should remove the {xpack} +plugin before upgrading to 6.4 or any later versions. More instructions +available in <> and <>. + +========================================= + * <> * <> diff --git a/docs/reference/release-notes/6.4.asciidoc b/docs/reference/release-notes/6.4.asciidoc index f39684627b163..bafcdd3acd68c 100644 --- a/docs/reference/release-notes/6.4.asciidoc +++ b/docs/reference/release-notes/6.4.asciidoc @@ -98,9 +98,18 @@ Caused by: org.elasticsearch.common.xcontent.XContentParseException: [-1:####] [ ====================================================== +[IMPORTANT] +.bin/plugin can no longer remove x-pack +========================================= + +`bin/plugin remove x-pack` no longer works. You should remove the {xpack} +plugin before upgrading to 6.4 or any later versions. + +========================================= + [float] === Known issues -See the important section above. +See the important sections above. {es} 6.4.0 fails to start when PEM encoded private key files that have been exported from `PKCS#12` keystores are in use. These files can be identified by the existence of lines that start with either