Gitlab update db migration failed because of the column `allow_proxy_whitelist` rename
We have several self-hosted gitlab instances as a paying customer which run with 13.8.6. We upgraded them to 13.9.6 with zero-downtime and gitlab-rake db:migrate
failed with errors like
"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",
Then we saw an issue#324160 where it was recommended to drop the old triggers asset_proxy_whitelist
and run the migrations again. But that didn't work for us. Now we get the same error with the newer allowlist
triggers
PG::DependentObjectsStillExist: ERROR: cannot drop column asset_proxy_allowlist of table application_settings because other objects depend on it
DETAIL: trigger trigger_22a39c5c25f3 on table application_settings depends on column asset_proxy_allowlist of table application_settings
Is there a way to solve this problem or role back and upgrade without problems?
Edited by Felix Imboden