Skip to content

Commit ccc986f

Browse files
zheng022Copilotmanue1mchammer01
authored
add information on running conifg apply after upgrade a node (#58180)
Co-authored-by: Copilot <[email protected]> Co-authored-by: Manuel Bergler <[email protected]> Co-authored-by: mc <[email protected]>
1 parent 7c65cc0 commit ccc986f

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

content/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,9 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
6060
tail -f /data/user/common/ghe-config.log
6161
```
6262

63+
The configuration runs in the background and you don't need to run `ghe-config-apply` explicitly unless you encounter a problem.
64+
> [!WARNING] If you are upgrading a node in a multi-node cluster, running `ghe-config-apply` on the command line or saving settings in the {% data variables.enterprise.management_console %} may fail and result in an incomplete upgrade if not all the nodes are upgraded to the same version. Please use `ghe-single-config-apply` instead.
65+
6366
1. Optionally, after the upgrade, validate the upgrade by configuring an IP exception list to allow access to a specified list of IP addresses. See [AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list).
6467
1. For single node upgrades, perform any post-upgrade tasks including disabling maintenance mode so users can use {% data variables.location.product_location %}.
6568

0 commit comments

Comments
 (0)