Error displaying incidents

Summary

Impossible to display the list of incidents

Steps to reproduce

Go to the incident list of a project

Example Project

What is the current bug behavior?

When I want to display the incident list, I get a label saying

There was an error displaying the incidents.

What is the expected correct behavior?

The incident list is displayed

Relevant logs and/or screenshots

Some important infos have been replaced by Xs. But as you can see the page outputs OK 200

Started GET "/xxx/ansible/playbooks/-/incidents" for XXX at 2020-09-03 15:04:45 +0200
Processing by Projects::IncidentsController#index as HTML
  Parameters: {"namespace_id"=>"xxx/ansible", "project_id"=>"playbooks"}
Completed 200 OK in 67ms (Views: 45.4ms | ActiveRecord: 8.9ms | Elasticsearch: 0.0ms | Allocations: 53201)

Capture_d_écran_de_2020-09-03_14-41-12

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 13.6.0 ? ... OK (13.6.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 13 users of 100 limit.


Checking LDAP ... Finished


Checking GitLab App ...


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: ...
11/1 ... yes
11/2 ... yes
11/3 ... yes
11/4 ... yes
5/5 ... yes
11/6 ... yes
11/7 ... yes
5/8 ... yes
12/10 ... yes
12/11 ... yes
5/12 ... yes
14/13 ... yes
14/14 ... yes
14/15 ... yes
14/16 ... yes
14/17 ... yes
14/18 ... yes
14/19 ... yes
6/20 ... yes
14/21 ... yes
15/23 ... yes
15/24 ... yes
15/25 ... yes
16/26 ... yes
16/27 ... yes
19/28 ... yes
19/29 ... yes
5/30 ... yes
21/31 ... yes
6/32 ... yes
10/33 ... yes
12/34 ... yes
10/35 ... yes
10/36 ... yes
12/37 ... yes
12/38 ... yes
10/39 ... yes
10/40 ... yes
10/48 ... yes
4/49 ... yes
23/50 ... yes
23/51 ... yes
10/52 ... yes
8/53 ... yes
21/55 ... yes
21/56 ... yes
10/57 ... yes
15/58 ... yes
27/59 ... yes
16/60 ... yes
28/61 ... yes
29/63 ... yes
29/64 ... yes
5/65 ... yes
Redis version >= 4.0.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.6)
Git version >= 2.24.0 ? ... yes (2.28.0)
Git user has default SSH configuration? ... yes
Active users: ... 14
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished
Edited by X