Changing Users to a more restrictive Permission in a Group causes GitLab error message and 404 errors
Summary
Changing Users to more restrictive permissions in a Group causes GitLab to issue 'Something went wrong on our end.' The new permissions partially take affect. A resource that they no longer have access to still appears but produces 404 errors. Refreshing the page, deleting local cache, re-opening browser doesn't fix the error.
Steps to reproduce
- Add User to a group with Reporter permission.
- Have User log in and log out.
- Change User to a group to Guest permission.
- User now logs in and sees 'Something went wrong on our end.' error.
What is the current bug behavior?
Error Message and 404s.
What is the expected correct behavior?
New Restrictive Permission should take affect and resources the User no longer has access to shouldn't appear and cause 404 errors.
Relevant logs and/or screenshots
No errors in nginx error.log
Output of checks
Results of GitLab environment info
System information
System: Ubuntu 16.04
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.6.6
Bundler Version:1.13.7
Rake Version: 10.5.0
Redis Version: 3.2.5
Git Version: 2.11.1
Sidekiq Version:4.2.7
GitLab information
Version: 9.1.0
Revision: c3f0f14
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.0.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
Checking GitLab Shell ...
GitLab Shell version >= 5.0.2 ? ... OK (5.0.2)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
24/3 ... repository is empty
29/25 ... ok
2/34 ... repository is empty
8/42 ... repository is empty
33/43 ... ok
8/46 ... ok
8/47 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... 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: ...
24/3 ... yes
29/25 ... yes
2/34 ... yes
8/42 ... yes
33/43 ... yes
8/46 ... yes
8/47 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.11.1)
Active users: 18
Checking GitLab ... Finished