"An error occurred fetching the approval rules" message in general settings of project

Summary

When opening the admin area of one of the projects on our self-hosted Gitlab (11.10.4-ee), we see the message "An error occurred fetching the approval rules" and under Merge request approvals, the list of approvers is not showing. This causes us to not being able to approve any merge request.

Steps to reproduce

Add a merge request and go to approve it. This will fail. When going to Admin Area the error message will show under the General tab of the settings.

Example Project

Not possible to recreate the issue on here, but we have 4 projects with this issue.

What is the current bug behavior?

Can't approve merge requests even if we are in the approvers list.

What is the expected correct behavior?

We can approve a merge request if we are in the approvers list.

Relevant logs and/or screenshots

image image image

Results of GitLab environment info

Expand for output related to GitLab environment info

System information System: Proxy: no Current User: git Using RVM: no Ruby Version: 2.5.3p105 Gem Version: 2.7.6 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.18.1 Sidekiq Version:5.2.5 Go Version: unknown

GitLab information Version: 11.10.4-ee Revision: 88a3c791734 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 9.6.11 URL: http://10.67.72.168 HTTP Clone URL: http://10.67.72.168/some-group/some-project.git SSH Clone URL: git@10.67.72.168:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: yes Using Omniauth: yes Omniauth Providers:

GitLab Shell Version: 9.0.0 Repository storage paths:

  • default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 9.0.0 ? ... OK (9.0.0) 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 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 not verifying SSL hostname of LDAPS server 'ldap.dap:389' LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) DN: uid=dj,ou=named,dc=dap uid: dj DN: uid=bert,ou=named,dc=dap uid: bert DN: uid=kevin,ou=named,dc=dap uid: kevin DN: uid=pverbruggen,ou=named,dc=dap uid: pverbruggen DN: uid=rgys,ou=named,dc=dap uid: rgys DN: uid=nt,ou=named,dc=dap uid: nt DN: uid=wcools,ou=named,dc=dap uid: wcools DN: uid=acdegeus,ou=named,dc=dap uid: acdegeus DN: uid=ddelahaye,ou=named,dc=dap uid: ddelahaye DN: uid=uleonard,ou=named,dc=dap uid: uleonard DN: uid=suma,ou=named,dc=dap uid: suma DN: uid=ajit,ou=named,dc=dap uid: ajit DN: uid=bcarette,ou=named,dc=dap uid: bcarette DN: uid=jalvarez,ou=named,dc=dap uid: jalvarez DN: uid=pvanhorebeek,ou=named,dc=dap uid: pvanhorebeek DN: uid=apanny,ou=named,dc=dap uid: apanny DN: uid=tvanduuren,ou=named,dc=dap uid: tvanduuren DN: uid=lbaelen,ou=named,dc=dap uid: lbaelen DN: uid=smitea,ou=named,dc=dap uid: smitea DN: uid=bmunters,ou=named,dc=dap uid: bmunters DN: uid=locampo,ou=named,dc=dap uid: locampo DN: uid=speirsman,ou=named,dc=dap uid: speirsman DN: uid=jgrondman,ou=named,dc=dap uid: jgrondman DN: uid=benhirsch,ou=named,dc=dap uid: benhirsch DN: uid=odebie,ou=named,dc=dap uid: odebie DN: uid=hvanthournhout,ou=named,dc=dap uid: hvanthournhout DN: uid=yvindevogel,ou=named,dc=dap uid: yvindevogel DN: uid=jvangorp,ou=named,dc=dap uid: jvangorp DN: uid=ggyselynck,ou=named,dc=dap uid: ggyselynck DN: uid=jvangysel,ou=named,dc=dap uid: jvangysel DN: uid=sovandaele,ou=named,dc=dap uid: sovandaele DN: uid=bverhoeve,ou=named,dc=dap uid: bverhoeve DN: uid=bradeschouwer,ou=named,dc=dap uid: bradeschouwer DN: uid=kasdeblieck,ou=named,dc=dap uid: kasdeblieck DN: uid=efannoy,ou=named,dc=dap uid: efannoy

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: ... 5/2 ... yes 20/4 ... yes 25/5 ... yes 25/6 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.5.3) Git version >= 2.18.0 ? ... yes (2.18.1) Git user has default SSH configuration? ... yes Active users: ... 22 Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes

No fix until now.

Edited May 23, 2019 by Kevin Andriessens
Assignee Loading
Time tracking Loading