A user can create new projects even if Personal projects limit =0 and Default projects limit = 0"

Summary

A user can create new projects even if Personal projects limit is 0 and Default projects limit is also 0

Steps to reproduce

Create a new user with Personal projects limit equal to zero and configure default projects limit to 0 in settings >> Account and Limit Settings

With this user create a new group.

Inside this new group the user can create a new project.

What is the current bug behavior?

User can create new projects even he/she should not be able to do it.

What is the expected correct behavior?

The user should not be able to create any new project.

Relevant logs and/or screenshots

erblin-profile-gitlab-edited

project-details-edited

default-limit-gitlab

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		CentOS 6.6
Current User:	git
Using RVM:	no
Ruby Version:	2.3.5p376
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.4
Go Version:	unknown


GitLab information
Version:	10.3.4
Revision:	56dc722
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://xxxxx
HTTP Clone URL:	https://xxxxx
SSH Clone URL:	ssh://xxxxx
Using LDAP:	yes
Using Omniauth:	no


GitLab Shell
Version:	5.10.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 >= 5.10.2 ? ... OK (5.10.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: ...
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 ...


Server: ldapmain
LDAP authentication... Success
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: ...
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 301


Checking GitLab ... Finished
Edited by Pablo Escobar