503 on multiple project subpages

Summary

After creating a branch + merge request from the issue UI, several project subpages are unreachable with 503 (Service Unavailable).

Steps to reproduce

  1. Navigate to an issue
  2. Create a branch + merge request (default name)
  3. Try to open Branches or Pipelines in project

What is the current bug behavior?

Page load fails with 503 (Service Unavailable). Problem occurs consistently at Branches and sporadically at Pipelines.

Furthermore, the problem appears isolated to the project. That project has the following features active:

  • Repository
  • Issue Tracking
  • Merge Requests
  • CI/CD via shared runner (also upgraded to 10.7.0)
  • Container Registry

Repository check for the project passes and all other projects work normally. Deleting the newly created merge request and branch appears to fix the problem.

Relevant logs and/or screenshots

Processing by Projects::PipelinesController#index as JSON

Parameters: {"scope"=>"all", "page"=>"1", "namespace_id"=>"my-namespace", "project_id"=>"my-project"}

Gitlab::Git::CommandError (2:NoMethodError: undefined method `call' for nil:NilClass
Did you mean? caller
Did you mean? caller):
lib/gitlab/git/repository.rb:1372:in `rescue in gitaly_migrate'
lib/gitlab/git/repository.rb:1365:in `gitaly_migrate'
lib/gitlab/git/commit.rb:234:in `batch_by_oid'
app/models/repository.rb:114:in `commits_by'
app/models/commit.rb:102:in `block (2 levels) in lazy'
app/models/commit.rb:99:in `each'
app/models/commit.rb:99:in `block in lazy'
app/models/ci/pipeline.rb:346:in `latest?'
app/serializers/base_serializer.rb:14:in `represent'
app/serializers/concerns/with_pagination.rb:17:in `represent'
app/serializers/pipeline_serializer.rb:23:in `represent'
app/controllers/projects/pipelines_controller.rb:44:in `block (2 levels) in index'
app/controllers/projects/pipelines_controller.rb:35:in `index'
lib/gitlab/i18n.rb:50:in `with_locale'
lib/gitlab/i18n.rb:56:in `with_user_locale'
app/controllers/application_controller.rb:326:in `set_locale'
lib/gitlab/middleware/multipart.rb:95:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:17:in `call'
lib/gitlab/etag_caching/middleware.rb:23:in `call'
lib/gitlab/middleware/read_only/controller.rb:28:in `call'
lib/gitlab/middleware/read_only.rb:16:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
lib/gitlab/middleware/release_env.rb:10:in `call'

Completed 503 Service Unavailable in 110ms (ActiveRecord: 21.3ms)

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		Debian 9.4
Current User:	git
Using RVM:	no
Ruby Version:	2.3.6p384
Gem Version:	2.6.13
Bundler Version:1.13.7
Rake Version:	12.3.0
Redis Version:	3.2.11
Git Version:	2.14.3
Sidekiq Version:5.0.5
Go Version:	unknown

GitLab information
Version:	10.7.0
Revision:	2011c9b
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://develop.briankintz.com
HTTP Clone URL:	https://develop.briankintz.com/some-group/some-project.git
SSH Clone URL:	git@develop.briankintz.com:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no


GitLab Shell
Version:	7.1.2
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 
Checking GitLab Shell ...

GitLab Shell version >= 7.1.2 ? ... OK (7.1.2)
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: ...
5/1 ... ok
4/2 ... ok
4/3 ... ok
6/4 ... ok
5/5 ... ok
6/6 ... ok
6/7 ... ok
6/8 ... 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: ...
5/1 ... yes
4/2 ... yes
4/3 ... yes
6/4 ... yes
5/5 ... yes
6/6 ... yes
6/7 ... yes
6/8 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.9.5 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 2


Checking GitLab ... Finished
Edited by 🤖 GitLab Bot 🤖