500 Error when creating Merge Request
Summary
Sometimes when i try to commit with the Webeditor and always when i try to create an Merge-Request i get an 500 Error.
Steps to reproduce
Two branches in a Groups Projekt which should be merged.
When i hit Submit Merge Request
i get a 500 Page.
What is the current bug behavior?
I can't create Merge Request or commit.
What is the expected correct behavior?
An created Merge Request or an commit.
Output of checks
Readiness
{
"db_check": {
"status": "ok"
},
"redis_check": {
"status": "ok"
},
"cache_check": {
"status": "ok"
},
"queues_check": {
"status": "ok"
},
"shared_state_check": {
"status": "ok"
},
"fs_shards_check": {
"status": "ok",
"labels": {
"shard": "default"
}
}
}
Liveness
{
"db_check": {
"status": "ok"
},
"redis_check": {
"status": "ok"
},
"cache_check": {
"status": "ok"
},
"queues_check": {
"status": "ok"
},
"shared_state_check": {
"status": "ok"
},
"fs_shards_check": {
"status": "ok"
}
}
Results of GitLab environment info
Expand for output related to GitLab environment info
root@GITLAB:~# gitlab-rake gitlab:env:infoSystem information
System: Ubuntu 16.04
Current User: git
Using RVM: no
Ruby Version: 2.3.5p376
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.0.0
Redis Version: 3.2.5
Git Version: 2.13.5
Sidekiq Version:5.0.4
Go Version: unknownGitLab information
Version: 10.0.3
Revision: 8895150
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://gitlab.support-pp.de
HTTP Clone URL: https://gitlab.support-pp.de/some-group/some-project.git
SSH Clone URL: git@gitlab.support-pp.de:some-group/some-project.git
Using LDAP: no Using Omniauth: noGitLab Shell Version: 5.9.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
root@GITLAB:~# gitlab-rake gitlab:check SANITIZE=true Checking GitLab Shell ...GitLab Shell version >= 5.9.0 ? ... OK (5.9.0) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 6/1 ... ok 6/2 ... ok 5/4 ... ok 6/6 ... ok 5/7 ... ok 6/8 ... ok 6/9 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 6/1 ... yes 6/2 ... yes 5/4 ... yes 6/6 ... yes 5/7 ... yes 6/8 ... yes 6/9 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.3 ? ... yes (2.3.5) Git version >= 2.7.3 ? ... yes (2.13.5) Git user has default SSH configuration? ... yes Active users: ... 7
Checking GitLab ... Finished