From 3f5ad23b1d3ae3a0c002253b2eb4abb608b00bd8 Mon Sep 17 00:00:00 2001 From: Fuzzwah Date: Wed, 16 Jul 2025 18:20:52 +1000 Subject: [PATCH 1/2] Clarify upgrade process for multi-node environments emphasizing that the upgrade of the primary needs to fully complete before doing other nodes. --- .../performing-an-upgrade/upgrading-with-an-upgrade-package.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md b/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md index 52a10976e9fb..14c4361552ec 100644 --- a/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md +++ b/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md @@ -67,7 +67,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea ## Upgrading an instance with multiple nodes using an upgrade package -To upgrade an instance that comprises multiple nodes using an upgrade package, you must upgrade the primary node, then upgrade any additional nodes. +To upgrade a multi-node GitHub Enterprise Server environment using an upgrade package, you must first upgrade the primary node and wait for its configuration run to complete successfully. Only after the primary is fully upgraded and configured can you proceed to upgrade any replica or additional nodes. Attempting to upgrade other nodes before the primary is complete will result in upgrade failures. * [Upgrading the primary node with an upgrade package](#upgrading-the-primary-node-with-an-upgrade-package) * [Upgrading additional nodes with an upgrade package](#upgrading-additional-nodes-with-an-upgrade-package) From a18ce0d33c90b6ca7aa50519e731c6d2d0b90eff Mon Sep 17 00:00:00 2001 From: Sharra-writes Date: Wed, 16 Jul 2025 10:51:25 -0700 Subject: [PATCH 2/2] Update content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md --- .../performing-an-upgrade/upgrading-with-an-upgrade-package.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md b/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md index 14c4361552ec..c3fa15f14fb5 100644 --- a/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md +++ b/content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md @@ -67,7 +67,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea ## Upgrading an instance with multiple nodes using an upgrade package -To upgrade a multi-node GitHub Enterprise Server environment using an upgrade package, you must first upgrade the primary node and wait for its configuration run to complete successfully. Only after the primary is fully upgraded and configured can you proceed to upgrade any replica or additional nodes. Attempting to upgrade other nodes before the primary is complete will result in upgrade failures. +To upgrade a multi-node {% data variables.product.prodname_ghe_server %} environment using an upgrade package, you must first upgrade the primary node and wait for its configuration run to complete successfully. Only after the primary is fully upgraded and configured can you proceed to upgrade any replica or additional nodes. Attempting to upgrade other nodes before the primary is complete will result in upgrade failures. * [Upgrading the primary node with an upgrade package](#upgrading-the-primary-node-with-an-upgrade-package) * [Upgrading additional nodes with an upgrade package](#upgrading-additional-nodes-with-an-upgrade-package)