sameersbn / sameersbn/docker-gitlab

Having issue in update the latest version of GitLAB.

Open
#1,413 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Gitlab update failed in db migration. The exception trace is given below for your reference,

2017-11-19T05:56:34.673873000Z Migrating database...
2017-11-19T05:56:48.807180000Z Missing Rails.application.secrets.jws_private_key for production environment. The secret will be generated and stored in config/secrets.yml.
2017-11-19T05:56:50.217117000Z rake aborted!
2017-11-19T05:56:50.217417000Z StandardError: An error has occurred, all later migrations canceled:
2017-11-19T05:56:50.217937000Z namespace directory cannot be moved
2017-11-19T05:56:50.218209000Z /home/git/gitlab/app/models/concerns/storage/legacy_namespace.rb:20:in block in move_dir' 2017-11-19T05:56:50.218459000Z /home/git/gitlab/app/models/concerns/storage/legacy_namespace.rb:11:in each'
2017-11-19T05:56:50.218705000Z /home/git/gitlab/app/models/concerns/storage/legacy_namespace.rb:11:in move_dir' 2017-11-19T05:56:50.218976000Z /home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:432:in block in make_lambda'
2017-11-19T05:56:50.219234000Z /home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:228:in block in halting_and_conditional' 2017-11-19T05:56:50.232695000Z /home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in <top (required)>'
2017-11-19T05:56:50.232922000Z Gitlab::UpdatePathError: namespace directory cannot be moved

@solidnerd Kindly help me to resolve this issue.

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 app/models/concerns/storage/legacy_namespace.rb, especially move_dir, and review the database migration output showing “namespace directory cannot be moved.” Reproduce the GitLab update migration and identify the storage condition causing the failure; done means the migration completes without the Gitlab::UpdatePathError.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.