Commit 84cb92aa authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'remove-ref-13.9-patch-geo' into 'master'

Geo - remove reference to 13.9 patch

See merge request gitlab-org/gitlab!64880
parents 3b143c7a 7fef8643
...@@ -18,9 +18,8 @@ We found an [issue with Git clone/pull through HTTP(s)](https://gitlab.com/gitla ...@@ -18,9 +18,8 @@ We found an [issue with Git clone/pull through HTTP(s)](https://gitlab.com/gitla
## Updating to GitLab 13.9 ## Updating to GitLab 13.9
We've detected an issue [with a column rename](https://gitlab.com/gitlab-org/gitlab/-/issues/324160) 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. that will prevent upgrades to GitLab 13.9.0, 13.9.1, 13.9.2 and 13.9.3 when following the zero-downtime steps. It is necessary
We are working on a patch, but until a fixed version is released, you can manually complete to perform the following additional steps for the zero-downtime upgrade:
the zero-downtime upgrade:
1. Before running the final `sudo gitlab-rake db:migrate` command on the deploy node, 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`) execute the following queries using the PostgreSQL console (or `sudo gitlab-psql`)
...@@ -40,9 +39,18 @@ the zero-downtime upgrade: ...@@ -40,9 +39,18 @@ the zero-downtime upgrade:
``` ```
If you have already run the final `sudo gitlab-rake db:migrate` command on the deploy node and have 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 encountered the [column rename issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324160), you will
follow the previous steps to complete the update. see the following error:
```shell
-- remove_column(:application_settings, :asset_proxy_whitelist)
rake aborted!
StandardError: An error has occurred, all later migrations canceled:
PG::DependentObjectsStillExist: ERROR: cannot drop column asset_proxy_whitelist of table application_settings because other objects depend on it
DETAIL: trigger trigger_0d588df444c8 on table application_settings depends on column asset_proxy_whitelist of table application_settings
```
To work around this bug, follow the previous steps to complete the update.
More details are available [in this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324160). More details are available [in this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324160).
## Updating to GitLab 13.7 ## Updating to GitLab 13.7
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment