-
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
Unable to upgrade from 16.1.5 #2954
Comments
Same issue here |
@LewS it took some time experimenting , but I successfully migrated from ancient source-installed Gitlab to Docker latest - 1. Posting here what I did as a reference:
#wait-until-background-migrations-are-done after each update. #checkout_source_tagThe target image is not available at Steps:
Now repeat steps 4 to 11 whenever image is missing. #wait-until-background-migrations-are-doneAfter bringing the Gitlab Docker container up, go to Admin -> Monitoring -> Background Migrations. Wait until you no longer have error 502, and then until every migration is done. #psql_repo_fixOlder Gitlab images use removed PostgreSQL Ubuntu repository. Not a problem. You need to replace it in #14_2_5After Background Migrations are done:
#15_4_6Wait until said migration is in process, then:
Referenceshttps://gitlab-com.gitlab.io/support/toolbox/upgrade-path/?current=13.4.7&distro=docker&edition=ce&n1=true |
I found out why I got "6 is not a known status value" for me there was two migrations that had something wrong in the status field. I changed status to 5 on both in postgresql and then I could upgrade past 16.1.5. |
OMG I could kiss you - THIS! - exactly what we needed. Thank you. Note that the steps here don't quite match recommended upgrade path from https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/ Focusing on the critical path: These require #psql_repo_fix: Here onwards no longer need #psql_repo_fix (build will fail) |
I've successfully upgraded a 12.4.2 clone to 16.1.5 with an aim to upgrade beyond to the latest, however whenever I change the docker-gitlab version above 16.1.5 we encounter a previously described error in the db migration script in...
"6 is not a known status value
/home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/state_collection.rb:78:in `match!'"
This was previously described in #2938 which was closed with reference to it already being listed in #2944, however the later details the inability to upgrade from 15.7.0 to 17.0.0 with reference to postgres, whereas #2938 details gitlab 16.1.6 to 16.3.7; my problem is to upgrade from 16.1.5 to anything higher (aside from the missing 16.1.6).
16.1.5 is running with a migrated pg 15 running via aws RDS.
Are we able to get some clarity on how we are getting a status value that is not known, and what we can do to move past it?
The text was updated successfully, but these errors were encountered: