sameersbn / sameersbn/docker-gitlab
v7.10.0 backup failed?
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
It seems to have imported the repos successfully, but then this error shows up at the end:
rake aborted!
NoMethodError: undefined method `chomp' for nil:NilClass
/home/git/gitlab/lib/tasks/gitlab/task_helpers.rake:60:in `prompt'
/home/git/gitlab/lib/tasks/gitlab/task_helpers.rake:22:in `ask_to_continue'
/home/git/gitlab/lib/tasks/gitlab/shell.rake:103:in `setup'
/home/git/gitlab/lib/tasks/gitlab/shell.rake:77:in `block (3 levels) in <top (required)>'
/home/git/gitlab/lib/tasks/gitlab/backup.rake:33:in `block (3 levels) in <top (required)>'
Tasks: TOP => gitlab:shell:setup
(See full trace by running task with --trace)
Put GitLab hooks in repositories dirs [DONE]
done
Restoring uploads ...
done
This will rebuild an authorized_keys file.
You will lose any data stored in authorized_keys file.
Trying to restore a v7.10.0 backup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with lib/tasks/gitlab/task_helpers.rake, especially prompt and ask_to_continue, then trace the call from lib/tasks/gitlab/shell.rake into lib/tasks/gitlab/backup.rake. Reproduce the v7.10.0 backup restore and verify that the restore completes without the NoMethodError shown in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100