sameersbn / sameersbn/docker-gitlab

Migration issue from 13.0.0 to 13.0.6

Open
#2,182 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

gitlab | Migrating database...
gitlab | 2020-06-24 00:04:46,665 CRIT Supervisor running as root (no user in config file)
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/gitaly.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/groups.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/puma.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
gitlab | 2020-06-24 00:04:46,665 INFO Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
gitlab | 2020-06-24 00:04:46,673 INFO RPC interface 'supervisor' initialized
gitlab | 2020-06-24 00:04:46,673 CRIT Server 'unix_http_server' running without any HTTP authentication checking
gitlab | 2020-06-24 00:04:46,673 INFO supervisord started with pid 626
gitlab | 2020-06-24 00:04:47,675 INFO spawned: 'gitaly' with pid 647
gitlab | 2020-06-24 00:04:47,677 INFO spawned: 'puma' with pid 648
gitlab | 2020-06-24 00:04:47,678 INFO spawned: 'gitlab-workhorse' with pid 649
gitlab | 2020-06-24 00:04:47,680 INFO spawned: 'sidekiq' with pid 650
gitlab | 2020-06-24 00:04:47,682 INFO spawned: 'nginx' with pid 652
gitlab | 2020-06-24 00:04:47,683 INFO spawned: 'sshd' with pid 653
gitlab | 2020-06-24 00:04:47,685 INFO spawned: 'cron' with pid 657
gitlab | 2020-06-24 00:04:48,750 INFO success: gitaly entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | 2020-06-24 00:04:48,751 INFO success: puma entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | 2020-06-24 00:04:48,751 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | 2020-06-24 00:04:48,751 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | 2020-06-24 00:04:48,751 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | 2020-06-24 00:04:48,751 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | 2020-06-24 00:04:48,751 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab | Missing Rails.application.secrets.openid_connect_signing_key for production environment. The secret will be generated and stored in config/secrets.yml.
gitlab | rake aborted!
gitlab | Your current database version is too old to be migrated. You should upgrade to GitLab 11.11.0 before moving to this version. Please see https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations
gitlab | /home/git/gitlab/lib/tasks/migrate/schema_check.rake:13:in block in <top (required)>' gitlab | /home/git/gitlab/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/exe/rake:27:in <top (required)>'
version: '2'
gitlab | Tasks: TOP => db:migrate => schema_version_check
gitlab | (See full trace by running task with --trace)
gitlab exited with code 1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the migration failure in lib/tasks/migrate/schema_check.rake and the db:migrate => schema_version_check task shown in the log. Review the referenced upgrade recommendations to determine the supported path from the reported version. Done should identify a reproducible fix or clearly document the required migration sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.