sameersbn / sameersbn/docker-gitlab
GRPC::Unavailable: 14:Connect 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
There is a bug when you backup/restore with command like this...
# backup
docker-compose run --rm gitlab app:rake gitlab:backup:create
# restore
docker-compose run --rm gitlab app:rake gitlab:backup:restore BACKUP=***
the info like this...
...
Dumping repositories ...
* liyeheng/gs-spring-boot-docker ... [WARNING] Executing 14:Connect Failed
Ignoring error on liyeheng/gs-spring-boot-docker - Failed to backup repo
[DONE]
rake aborted!
GRPC::Unavailable: 14:Connect Failed
/home/git/gitlab/vendor/bundle/ruby/2.4.0/gems/grpc-1.11.0-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:31:in `check_status'
...
To see #1655 , @serenader2014 supply a way to handle issue but can't reslove it.
My Gitlab version is 10.6.2, and I use the version 11.3.5, it still has the problem...
Can you fix it ? Thanks...
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 by reproducing the documented docker-compose backup and restore commands and reviewing issue #1655 alongside the GRPC::Unavailable trace. Done means repository backup and restore complete without the Connect Failed error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, ruby
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100