Skip to content
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.

Sign up for GitHub

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

Jump to bottom

missing 16.1.6 and 16.3.7 version needed for upgrade path #2938

Open
RickSKy opened this issue May 1, 2024 · 14 comments
Open

missing 16.1.6 and 16.3.7 version needed for upgrade path #2938

RickSKy opened this issue May 1, 2024 · 14 comments

Comments

@RickSKy
Copy link

RickSKy commented May 1, 2024

refer to gitlab offical website, 16.1.6 and 16.3.7 version is needed for upgrading.
https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/?current=16.0.0&distro=docker&edition=ce
@mihelm
Copy link

mihelm commented May 4, 2024

@RickSKy I doubt that 16.1.6 is a firm requirement — I think they're just listing 16.1.6 because that was the last bug-fix update for 16.1. You should be able to go to 16.2.x from 16.1.5. You could probably skip 16.2.x, but I personally prefer not to skip minor versions. Just take the latest .x available for each minor version and you should be fine.

@RickSKy
Copy link
Author

RickSKy commented May 6, 2024

I am confused and trying to upgrade GitLab 15.6 to 16.11. I followed the official instructions for the upgrade (referencing https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/?current=15.6.0&distro=docker&edition=ce). Since there is no 16.1.6 version available, I upgraded to 16.1.5. Then, I attempted to upgrade to 16.3.7, but encountered an error. I then tried upgrading to 16.2.0, but received the same error message.

@RickSKy
Copy link
Author

RickSKy commented May 9, 2024

image
image

@brucewu16899
Copy link

I followed the official guidance to upgrade from version 15.7.1 to 16.11.1. However, the versions provided by sameersbn/docker-gitlab are missing 16.1.6 and 16.3.7, which has caused the upgrade process to be incomplete. I earnestly request the development team to supply these two missing versions. Thank you. 🙇

@mihelm
Copy link

mihelm commented May 9, 2024

@RickSKy @brucewu16899 I assume you have updated your database from postgresql 12? Support for that was dropped with GitLab 16, so I'm assuming you already updated your database before you even got to this point.

@mihelm
Copy link

mihelm commented May 9, 2024

@RickSKy And regarding your attempt to upgrade to 16.2.0: 16.2.8 probably would have been a better idea, since 16.1.5 will almost certainly have contained backported fixes that weren't in 16.2.0.

@RickSKy
Copy link
Author

RickSKy commented May 10, 2024

@mihelm
image
Before upgrading 15.6, the first step was to upgrade Postgres to 14, as shown in the figure. Following the official upgrade path, it is possible to upgrade to 16.3.7 after upgrading to 16.1.6. Therefore, I tried to upgrade to 16.3.6 and several versions before 16.3.6 after successfully upgrading to 16.1.5. The errors displayed in the logs all seem to be the same.

@mihelm
Copy link

mihelm commented May 10, 2024

@RickSKy Thanks for clarifying the postgresql version — I just wanted to rule out the database version as an issue, since that hit around the time these gitlab versions came out.

I have no idea what's tripping it up from the stack trace you posted. Can you post the complete log from an attempted startup as text instead of screenshots? And maybe just for testing remove the restart: always from just the gitlab container, so it doesn't loop and it's easier to see where one attempt starts and where it ends.

I do hope you have a backup from the last few versions where it was running properly?

@brucewu16899
Copy link

brucewu16899 commented May 15, 2024 •
edited
Loading

@mihelm
I'm currently using version 15.7.6 of sameersbn/docker-gitlab.
The official recommended update process for GitLab is
15.11.13 => 16.1.6 => 16.3.7 => 16.7.7 => 16.11.2.
However, my personal update process deviated slightly:
15.11.13 => 16.1.5 => 16.1.6 => 16.3.6 => 16.3.7 => 16.5.2 => 16.7.7 => 16.11.2.
Prior to updating to 16.5.2, I was using the version sameersbn/postgresql:12-20200524 for PostgreSQL.
When updating to 16.5.2, I simultaneously upgraded PostgreSQL to sameersbn/postgresql:14-20230628.
Additionally, I made modifications to relevant procedures within sameersbn/docker-gitlab and
build docker images of localhost for versions 16.1.6 and 16.3.7 of GitLab.
Through this update process, I successfully transitioned from sameersbn/docker-gitlab 15.7.6 to 16.11.2.

@RickSKy You can try the update process mentioned above. Wishing you a successful update!

@RickSKy
Copy link
Author

RickSKy commented May 16, 2024

@brucewu16899 @mihelm thanks， I have build 16.1.6 locally and update from 16.1.5 to 16.1.6 succussfully. then try to update to 16.3.7, the error log is same with before:

gitlab-1             | Installing configuration templates...
gitlab-1             | SSL Key, SSL Certificate and DHParam were not found.
gitlab-1             | Assuming that the container is running behind a HTTPS enabled load balancer.
gitlab-1             | Configuring gitlab...
gitlab-1             | Configuring gitlab::database..
gitlab-1             | Configuring /home/git/.postgresqlrc to avoid version mismatch on dumping
gitlab-1             | - Detected server version: 140008
gitlab-1             | - Generating /home/git/.postgresqlrc
gitlab-1             | 14 gitlab_postgresql:5432 gitlabhq_production
gitlab-1             | - Uninstalling unused client(s): postgresql-client-13 postgresql-client-15 postgresql-client-16
gitlab-1             | Configuring gitlab::redis
gitlab-1             | Configuring gitlab::actioncable
gitlab-1             | Configuring gitlab::secrets...
gitlab-1             | Configuring gitlab::sidekiq...
gitlab-1             | Configuring gitlab::gitaly...
gitlab-1             | Configuring gitlab::monitoring...
gitlab-1             | Configuring gitlab::gitlab-workhorse...
gitlab-1             | Configuring gitlab::puma...
gitlab-1             | Configuring gitlab::timezone...
gitlab-1             | Configuring gitlab::rack_attack...
gitlab-1             | Configuring gitlab::ci...
gitlab-1             | Configuring gitlab::artifacts...
gitlab-1             | Configuring gitlab::packages...
gitlab-1             | Configuring gitlab::terraform_state...
gitlab-1             | Configuring gitlab::lfs...
gitlab-1             | Configuring gitlab::uploads...
gitlab-1             | Configuring gitlab::mattermost...
gitlab-1             | Configuring gitlab::project_features...
gitlab-1             | Configuring gitlab::oauth...
gitlab-1             | Configuring gitlab::ldap...
gitlab-1             | Configuring gitlab::cron_jobs...
gitlab-1             | Configuring gitlab::backups...
gitlab-1             | Configuring gitlab::backups::schedule...
gitlab-1             | Configuring gitlab::registry...
gitlab-1             | Configuring gitlab::pages...
gitlab-1             | Configuring gitlab::sentry...
gitlab-1             | Configuring gitlab::content_security_policy...
gitlab-1             | Configuring gitlab-shell...
gitlab-1             | Configuring nginx...
gitlab-1             | Configuring nginx::gitlab...
gitlab-1             | Configuring nginx::gitlab::hsts...
gitlab-1             | Migrating database...
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/gitaly.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/groups.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,687 INFO Included extra file "/etc/supervisor/conf.d/puma.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,688 INFO Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,688 INFO Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
gitlab-1             | 2024-05-16 07:08:44,688 INFO Set uid to user 0 succeeded
gitlab-1             | 2024-05-16 07:08:44,698 INFO RPC interface 'supervisor' initialized
gitlab-1             | 2024-05-16 07:08:44,699 INFO supervisord started with pid 1677
gitlab-1             | 2024-05-16 07:08:45,705 INFO spawned: 'gitaly' with pid 1690
gitlab-1             | 2024-05-16 07:08:45,711 INFO spawned: 'puma' with pid 1691
gitlab-1             | 2024-05-16 07:08:45,718 INFO spawned: 'gitlab-workhorse' with pid 1692
gitlab-1             | 2024-05-16 07:08:45,724 INFO spawned: 'sidekiq' with pid 1693
gitlab-1             | 2024-05-16 07:08:45,730 INFO spawned: 'sshd' with pid 1694
gitlab-1             | 2024-05-16 07:08:45,736 INFO spawned: 'nginx' with pid 1700
gitlab-1             | 2024-05-16 07:08:45,742 INFO spawned: 'cron' with pid 1701
gitlab-1             | 2024-05-16 07:08:47,290 INFO success: gitaly entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | 2024-05-16 07:08:47,291 INFO success: puma entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | 2024-05-16 07:08:47,291 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | 2024-05-16 07:08:47,291 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | 2024-05-16 07:08:47,291 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | 2024-05-16 07:08:47,291 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | 2024-05-16 07:08:47,291 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab-1             | /home/git/gitlab/lib/gitlab/instrumentation/redis.rb:9: warning: already initialized constant Gitlab::Instrumentation::Redis::ActionCable
gitlab-1             | /home/git/gitlab/lib/gitlab/instrumentation/redis.rb:9: warning: previous definition of ActionCable was here
gitlab-1             | rake aborted!
gitlab-1             | StandardError: An error has occurred, all later migrations canceled:
gitlab-1             |
gitlab-1             | 6 is not a known status value
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/state_collection.rb:78:in `match!'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:123:in `transition_for'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:154:in `fire'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:219:in `block in add_actions'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/machine.rb:729:in `block (2 levels) in define_helper'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:224:in `block in add_actions'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/machine.rb:729:in `block (2 levels) in define_helper'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:77:in `finalize'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:10:in `finalize'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:160:in `block (2 levels) in finalize_batched_background_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/query_analyzers/base.rb:39:in `with_suppressed'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:159:in `block in finalize_batched_background_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/reestablished_connection_stack.rb:21:in `with_restored_connection_stack'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:158:in `finalize_batched_background_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:231:in `ensure_batched_background_migration_is_finished'
gitlab-1             | /home/git/gitlab/db/post_migrate/20230618020202_finish_user_type_migration.rb:11:in `up'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:873:in `public_send'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:873:in `exec_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migration_helpers/restrict_gitlab_schema.rb:33:in `block in exec_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/query_analyzer.rb:37:in `within'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migration_helpers/restrict_gitlab_schema.rb:30:in `exec_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migration_helpers/automatic_lock_writes_on_tables.rb:21:in `exec_migration'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:854:in `block (2 levels) in migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:853:in `block in migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in `with_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:852:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1046:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1360:in `block in execute_migration_in_transaction'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1413:in `ddl_transaction'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/lock_retry_mixin.rb:36:in `ddl_transaction'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1359:in `execute_migration_in_transaction'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/runner_backoff/active_record_mixin.rb:21:in `execute_migration_in_transaction'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1333:in `each'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1333:in `migrate_without_lock'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1282:in `block in migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1432:in `block in with_advisory_lock'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/pg_backend_pid.rb:15:in `block in with_advisory_lock_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in `with_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1447:in `with_advisory_lock_connection'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/pg_backend_pid.rb:12:in `with_advisory_lock_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1428:in `with_advisory_lock'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1282:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1117:in `up'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1092:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/tasks/database_tasks.rb:262:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/railties/databases.rake:92:in `block (2 levels) in <top (required)>'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/sentry-ruby-5.8.0/lib/sentry/rake.rb:26:in `execute'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
gitlab-1             | /usr/local/bin/bundle:23:in `load'
gitlab-1             | /usr/local/bin/bundle:23:in `<main>'
gitlab-1             |
gitlab-1             | Caused by:
gitlab-1             | ArgumentError: 6 is not a known status value
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/state_collection.rb:78:in `match!'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:123:in `transition_for'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:154:in `fire'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:219:in `block in add_actions'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/machine.rb:729:in `block (2 levels) in define_helper'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/event.rb:224:in `block in add_actions'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/state_machines-0.5.0/lib/state_machines/machine.rb:729:in `block (2 levels) in define_helper'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:77:in `finalize'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:10:in `finalize'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:160:in `block (2 levels) in finalize_batched_background_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/query_analyzers/base.rb:39:in `with_suppressed'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:159:in `block in finalize_batched_background_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/reestablished_connection_stack.rb:21:in `with_restored_connection_stack'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:158:in `finalize_batched_background_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:231:in `ensure_batched_background_migration_is_finished'
gitlab-1             | /home/git/gitlab/db/post_migrate/20230618020202_finish_user_type_migration.rb:11:in `up'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:873:in `public_send'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:873:in `exec_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migration_helpers/restrict_gitlab_schema.rb:33:in `block in exec_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/query_analyzer.rb:37:in `within'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migration_helpers/restrict_gitlab_schema.rb:30:in `exec_migration'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migration_helpers/automatic_lock_writes_on_tables.rb:21:in `exec_migration'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:854:in `block (2 levels) in migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:853:in `block in migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in `with_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:852:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1046:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1360:in `block in execute_migration_in_transaction'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1413:in `ddl_transaction'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/lock_retry_mixin.rb:36:in `ddl_transaction'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1359:in `execute_migration_in_transaction'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/runner_backoff/active_record_mixin.rb:21:in `execute_migration_in_transaction'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1333:in `each'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1333:in `migrate_without_lock'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1282:in `block in migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1432:in `block in with_advisory_lock'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/pg_backend_pid.rb:15:in `block in with_advisory_lock_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:215:in `with_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1447:in `with_advisory_lock_connection'
gitlab-1             | /home/git/gitlab/lib/gitlab/database/migrations/pg_backend_pid.rb:12:in `with_advisory_lock_connection'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1428:in `with_advisory_lock'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1282:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1117:in `up'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/migration.rb:1092:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/tasks/database_tasks.rb:262:in `migrate'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/railties/databases.rake:92:in `block (2 levels) in <top (required)>'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/sentry-ruby-5.8.0/lib/sentry/rake.rb:26:in `execute'
gitlab-1             | /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
gitlab-1             | /usr/local/bin/bundle:23:in `load'
gitlab-1             | /usr/local/bin/bundle:23:in `<main>'
gitlab-1             | Tasks: TOP => db:migrate
gitlab-1             | (See full trace by running task with --trace)

@kkimurak kkimurak mentioned this issue May 22, 2024
Closed
@LewS
Copy link

LewS commented Jun 20, 2024

I'm not sure why this was closed, the postgres issue linked has no bearing on this.
I have the same problem being stuck on 16.1.5 with any attempt to progress beyond this resulting in ArgumentError: 6 is not a known status value.

@LewS LewS mentioned this issue Jun 20, 2024
Open
@kkimurak
Copy link
Contributor

@LewS You may be misunderstanding:

By the way, I think the additionally commented issue (#2938 (comment) : migration aborted with message "6 is not a known status value") is a bit away from original purpose of this issue (that corresponding release of 16.1.6 and 16.3.7, which are in GitLab's official upgrade path, are not available as sameersbn/gitlab image).

I think it's fine to leave #2954 open to track the "additional issues" mentioned above but I'll leave it up to you to decide whether to close it or not.

@LewS
Copy link

LewS commented Jun 24, 2024

Thanks for the explanation @kkimurak, I clearly misread (or rather didn't) the status of this issue.
I agree regarding the original purpose of this issue, and will keep the other open to assist tracking relevant changes as you suggest.

@FluffyDiscord
Copy link

Could we please get these two missing versions? Running in to the same error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@brucewu16899 @FluffyDiscord @LewS @RickSKy @mihelm @kkimurak