-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A lot of page 500 when upgrading from 13.12.4 to 14.0.0 #2430
Comments
Hi, I neded to set these envs:
And I had to upgrade to the latest Redis because my ancient one didn't know the UNLINK command |
Thanks. |
When jumping direct to release 14.3.0 I get this rake migrate error: Do I need to go to 14.0.0 first? |
Yes of course. Please follow upgrade path. It says "latest 13.12.Z -> latest 14.0.Z -> latest 14.Y.Z" is supported. |
I tried to upgrade the following path and checked only if the login screen appeared: Between 14.1.3 and 14.2.1 I get the same rake aborted error and have no login screen |
There are some background migration tasks after container up, so you should not stop container even you can see login screen. Make sure that all of tasks are finished (you can check the status in /admin/background_migrations ). Also check #2409 |
I noticed 14.0.0 has a list of 5 active background migrations that seems to be stuck. All 0.00% after 1 hour up |
Thanks for checking up, then you can run background migration manually. See https://docs.gitlab.com/ee/user/admin_area/monitoring/background_migrations.html#manually-finishing-a-batched-background-migration |
After many OTP login attempts I got back in to view the list of waiting migrations:
After running
With two empty lines, so no information which task |
I think I got it working now. My steps:
|
I can upgrade up to gitlab version 13.12.4, but as soon as I go to 14.0.0 I'm facing a lot of page 500 errors.
When I turn 2FA off, it seems to work a bit better, but 2FA is required.
I tried to turn off 2FA in version 13.12.4 before starting the upgrade, but no luck.
The changes in my docker-compose file are:
So a lot is changing on redis side.
Does the mapped redis volume maybe contain some previous 2FA cache?
I tried to remove and add 2FA, but this didn't trigger any cache clean up I think
The text was updated successfully, but these errors were encountered: