diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-18 19:00:14 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-18 19:00:14 +0000 |
commit | 05f0ebba3a2c8ddf39e436f412dc2ab5bf1353b2 (patch) | |
tree | 11d0f2a6ec31c7793c184106cedc2ded3d9a2cc5 /doc/update/zero_downtime.md | |
parent | ec73467c23693d0db63a797d10194da9e72a74af (diff) | |
download | gitlab-ce-05f0ebba3a2c8ddf39e436f412dc2ab5bf1353b2.tar.gz |
Add latest changes from gitlab-org/gitlab@15-8-stable-eev15.8.0-rc42
Diffstat (limited to 'doc/update/zero_downtime.md')
-rw-r--r-- | doc/update/zero_downtime.md | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/update/zero_downtime.md b/doc/update/zero_downtime.md index deda12145da..a849033c3e5 100644 --- a/doc/update/zero_downtime.md +++ b/doc/update/zero_downtime.md @@ -456,7 +456,13 @@ Log in to your **primary** node, executing the following: 1. To get the database migrations and latest code in place, run: ```shell - sudo SKIP_POST_DEPLOYMENT_MIGRATIONS=true gitlab-ctl reconfigure + sudo gitlab-ctl reconfigure + ``` + +1. After the node is updated and reconfigure finished successfully, complete the migrations: + + ```shell + sudo SKIP_POST_DEPLOYMENT_MIGRATIONS=true gitlab-rake db:migrate ``` ### Update the Geo secondary site @@ -486,7 +492,7 @@ On each **secondary** node, executing the following: 1. To get the database migrations and latest code in place, run: ```shell - sudo SKIP_POST_DEPLOYMENT_MIGRATIONS=true gitlab-ctl reconfigure + sudo gitlab-ctl reconfigure ``` 1. Run post-deployment database migrations, specific to the Geo database: |