Skip to content

Commit f69121e

Browse files
[8.9] Removes non-backup rollback from upgrade kibana (elastic#189011) (elastic#189090)
# Backport This will backport the following commits from `main` to `8.9`: - [Removes non-backup rollback from upgrade kibana (elastic#189011)](elastic#189011) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christiane (Tina) Heiligers","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-07-24T14:51:24Z","message":"Removes non-backup rollback from upgrade kibana (elastic#189011)\n\nFIx https://github.com/elastic/kibana/issues/158117\r\n\r\nRemoves section on rolling back without a snapshot.\r\n\r\nThe changes made to kibana saved objects migration make the process of\r\nrolling back without a snapshot too complex for customers to do alone.\r\nFurthermore, rolling back without a snapshot is not recommended or\r\nsupported.\r\n\r\nSee the changes on `master`\r\n[here](https://kibana_bk_189011.docs-preview.app.elstc.co/guide/en/kibana/master/upgrade-migrations-rolling-back.html)\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f2aa1faee4b05f3aa2d8f21bb7e63aff357cdd9b","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","v8.8.0","v8.9.0","v8.10.0","v8.11.0","v8.12.0","v8.13.0","v8.14.0","v8.15.0","v8.16.0"],"title":"Removes non-backup rollback from upgrade kibana","number":189011,"url":"https://github.com/elastic/kibana/pull/189011","mergeCommit":{"message":"Removes non-backup rollback from upgrade kibana (elastic#189011)\n\nFIx https://github.com/elastic/kibana/issues/158117\r\n\r\nRemoves section on rolling back without a snapshot.\r\n\r\nThe changes made to kibana saved objects migration make the process of\r\nrolling back without a snapshot too complex for customers to do alone.\r\nFurthermore, rolling back without a snapshot is not recommended or\r\nsupported.\r\n\r\nSee the changes on `master`\r\n[here](https://kibana_bk_189011.docs-preview.app.elstc.co/guide/en/kibana/master/upgrade-migrations-rolling-back.html)\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f2aa1faee4b05f3aa2d8f21bb7e63aff357cdd9b"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.9","8.10","8.11","8.12","8.13","8.14","8.15"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.9","label":"v8.9.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.10","label":"v8.10.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.11","label":"v8.11.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.12","label":"v8.12.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/189011","number":189011,"mergeCommit":{"message":"Removes non-backup rollback from upgrade kibana (elastic#189011)\n\nFIx https://github.com/elastic/kibana/issues/158117\r\n\r\nRemoves section on rolling back without a snapshot.\r\n\r\nThe changes made to kibana saved objects migration make the process of\r\nrolling back without a snapshot too complex for customers to do alone.\r\nFurthermore, rolling back without a snapshot is not recommended or\r\nsupported.\r\n\r\nSee the changes on `master`\r\n[here](https://kibana_bk_189011.docs-preview.app.elstc.co/guide/en/kibana/master/upgrade-migrations-rolling-back.html)\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f2aa1faee4b05f3aa2d8f21bb7e63aff357cdd9b"}}]}] BACKPORT--> Co-authored-by: Christiane (Tina) Heiligers <[email protected]>
1 parent 3d21f90 commit f69121e

File tree

1 file changed

+0
-37
lines changed

1 file changed

+0
-37
lines changed

docs/setup/upgrade/rollback-migration.asciidoc

Lines changed: 0 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -30,40 +30,3 @@ POST _snapshot/my_repository/my_snapshot_2099.05.06/_restore
3030
--------------------------------------------
3131
<1> Exclude all indices and data streams from the restore operation to ensure that only the {kib} system indices included in the {kib} feature state will be restored.
3232
. Start all {kib} instances on the older version you want to rollback to.
33-
34-
[float]
35-
==== (Not supported) Roll back without a backup snapshot
36-
37-
WARNING: Rolling back without a backup snapshot is not supported and will be removed in a future version of {kib}.
38-
39-
. To make sure no {kib} instances are performing an upgrade migration, shut down all {kib} instances.
40-
. {ref}/snapshots-take-snapshot.html[Take a snapshot] that includes the `kibana` feature state. By default, snapshots include the `kibana` feature state.
41-
. Delete the version-specific indices created by the failed upgrade migration.
42-
+
43-
For example, to rollback from a failed upgrade
44-
to v7.12.0, enter:
45-
+
46-
[source,sh]
47-
--------------------------------------------
48-
DELETE /.kibana_7.12.0_*,.kibana_task_manager_7.12.0_*
49-
--------------------------------------------
50-
51-
. Inspect the output of `GET /_cat/aliases`.
52-
+
53-
If the `.kibana` or `.kibana_task_manager` aliases are missing, you must create them manually.
54-
Find the latest index from the output of `GET /_cat/indices` and create the missing alias to point to the latest index.
55-
For example, if the `.kibana` alias is missing, and the latest index is `.kibana_3`, create a new alias using:
56-
+
57-
[source,sh]
58-
--------------------------------------------
59-
POST /.kibana_3/_aliases/.kibana
60-
--------------------------------------------
61-
62-
. To remove the write block from the roll back indices, enter:
63-
+
64-
[source,sh]
65-
--------------------------------------------
66-
PUT /.kibana,.kibana_task_manager/_settings {"index.blocks.write": false}
67-
--------------------------------------------
68-
69-
. Start {kib} on the older version you want to roll back to.

0 commit comments

Comments
 (0)