I had to upgrade an old 13.6-ee installed via Debian 9 packages to the latest 14.4.1 as a docker version on a Debian 11. Like many people, I faced the hard problem of the 14.2.x upgrade failing because of the migrations. I tried the official solution which states that the problem has been solved and that it is sufficient to follow a very precise upgrade path, checking each time that the migrations are completed. I’m sorry to tell it: but like many people on the Internet, it never worked for me.
Failing being absolutely not an option, I tried harder and found this topic on the forum:
It was less or more my problem : the bigInt migrations were failing. So, like Dave Robertson I decided to manually modify the migration to check if it works. Finally, I deleted all migrations concerning bigInt. First I launched my docker, then I logged in immediately, and then I executed:
cd /opt/gitlab/embedded/service/gitlab-rails/db/post_migrate/ && rm *bigint*
It worked. Now, I finally have Gitlab working again… less or more.
Some things are not working (like the project activity not being updated, adding a new user to a project leading to a 500 (adding group works)). Maybe it’s related to the big Int migration problems, maybe not. But I’d like to finish correctly this upgrade, and maybe, help Gitlab team to release a new release that really work for everybody, even for people upgrading from 13.x in a docker installation.
So right now, when I go to monitoring health checks, I see:
20210701141346_finalize_ci_builds_stage_id_bigint_conversion.rb 20210706212710_finalize_ci_job_artifacts_bigint_conversion.rb 20210707210916_finalize_ci_stages_bigint_conversion.rb 20210708011426_finalize_ci_builds_metadata_bigint_conversion.rb 20210713042153_finalize_ci_sources_pipelines_bigint_conversion.rb 20210714015537_finalize_ci_build_trace_chunks_bigint_conversion.rb 20210802131812_finalize_convert_deployments_bigint.rb 20210804151444_prepare_indexes_for_ci_job_artifact_bigint_conversion.rb 20210804153307_prepare_indexes_for_tagging_bigint_conversion.rb 20210804154407_prepare_indexes_for_ci_stage_bigint_conversion.rb 20210805131510_finalize_ci_builds_runner_session_bigint_conversion.rb 20210806131706_finalize_taggins_bigint_conversion.rb 20210809143931_finalize_job_id_conversion_to_bigint_for_ci_job_artifacts.rb 20210817024335_prepare_indexes_for_events_bigint_conversion.rb 20210901044202_push_event_payloads_bigint_conversion_remove_triggers.rb 20210901044237_events_bigint_conversion_remove_triggers.rb 20210907013944_cleanup_bigint_conversion_for_ci_builds_metadata.rb 20210907021940_cleanup_bigint_conversion_for_ci_stages.rb 20210907033745_cleanup_bigint_conversion_for_deployments.rb 20210907041000_cleanup_bigint_conversion_for_geo_job_artifact_deleted_events.rb 20210907211557_finalize_ci_builds_bigint_conversion.rb 20210915022415_cleanup_bigint_conversion_for_ci_builds.rb
what would you suggest?
I think I’m going to check those migration one by one, and verify if the columns they apply to really exist.
What do you think?