Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
f37b14a3
Commit
f37b14a3
authored
May 17, 2021
by
Anton Smith
Committed by
Achilleas Pipinellis
May 17, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add warning about zero downtime updates to 13.9
parent
2ad579e5
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
2 deletions
+23
-2
doc/administration/geo/replication/version_specific_updates.md
...dministration/geo/replication/version_specific_updates.md
+23
-2
No files found.
doc/administration/geo/replication/version_specific_updates.md
View file @
f37b14a3
...
...
@@ -15,8 +15,29 @@ for updating Geo nodes.
We've detected an issue
[
with a column rename
](
https://gitlab.com/gitlab-org/gitlab/-/issues/324160
)
that may prevent upgrades to GitLab 13.9.0, 13.9.1, 13.9.2 and 13.9.3.
We are working on a patch and recommend delaying any upgrade attempt until a fixed version
is released.
We are working on a patch, but until a fixed version is released, you can manually complete
the zero-downtime upgrade:
1.
Before running the final
`sudo gitlab-rake db:migrate`
command on the deploy node,
execute the following queries using the PostgreSQL console (or
`sudo gitlab-psql`
)
to drop the problematic triggers:
```
sql
drop
trigger
trigger_e40a6f1858e6
on
application_settings
;
drop
trigger
trigger_0d588df444c8
on
application_settings
;
drop
trigger
trigger_1572cbc9a15f
on
application_settings
;
drop
trigger
trigger_22a39c5c25f3
on
application_settings
;
```
1.
Run the final migrations:
```
shell
sudo
gitlab-rake db:migrate
```
If you have already run the final
`sudo gitlab-rake db:migrate`
command on the deploy node and have
encountered the
[
column rename issue
](
https://gitlab.com/gitlab-org/gitlab/-/issues/324160
)
, you can still
follow the previous steps to complete the update.
More details are available
[
in this issue
](
https://gitlab.com/gitlab-org/gitlab/-/issues/324160
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment