From fd3e81ce1905b70c916756e89ea1f7af8be9af46 Mon Sep 17 00:00:00 2001 From: Stoney <19228888+ThatStoney@users.noreply.github.com> Date: Mon, 27 Dec 2021 09:42:38 -0500 Subject: [PATCH 1/2] Clarify hotpatch rollback instructions Replication does not need to be stopped before hotpatching, so most customers faced with a rollback will probably have replication running. Since replication can't be running for a package upgrade (which is how we roll back a hotpatch) we should include a reminder in our docs that replication will need to be stopped prior to rolling back. --- .../upgrading-github-enterprise-server.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 7d618961ca6f..2c25151d844f 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -225,7 +225,9 @@ If an upgrade fails or is interrupted, you should revert your instance back to i ### Rolling back a patch release -To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} +To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. Before rolling back, replication must be temporarly stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} + +Once the rollback is complete, re-enable replication by running `ghe-repl-start` on all replicas. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)." From f1b7abe04593c0b8cadfce1913a1c83ea2d0081f Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Thu, 6 Jan 2022 11:46:48 -0600 Subject: [PATCH 2/2] Apply @vgrl's suggestions Co-authored-by: Vanessa --- .../upgrading-github-enterprise-server.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 2c25151d844f..d1fe3ba6fdca 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -225,9 +225,9 @@ If an upgrade fails or is interrupted, you should revert your instance back to i ### Rolling back a patch release -To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. Before rolling back, replication must be temporarly stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} +To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. Before rolling back, replication must be temporarily stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} -Once the rollback is complete, re-enable replication by running `ghe-repl-start` on all replicas. +Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)."