creating a project called 'images' fail
Summary
While creating a new instance of gitlab, we run a script that consist of various calls to API, one of which create some default project with public docker images. The project is named images
and we put it under the build
group.
Steps to reproduce
install a fresh copy of gitlab ee and run the following:
URL="https://$DOMAIN/api/v4/groups?path=build&name=build&visibility=public"
curl -s -X POST "${URL}" -H "PRIVATE-TOKEN: ${TOKEN}"
URL="https://${DOMAIN}/api/v4/projects?name=images"
curl -s -X POST "${URL}" -H "PRIVATE-TOKEN: ${TOKEN}"
What is the current bug behavior?
When you run the curls above, the second one will return an error: Failed to create repository via gitlab-shell
$ curl -s -X POST "https://${DOMAIN}/api/v4/projects?name=images" -H "PRIVATE-TOKEN: ${TOKEN}"
{"message":{"base":["Failed to create repository via gitlab-shell"],"limit_reached":[]}}
but I can create other projects as long as the name is not images
What is the expected correct behavior?
Project should be created
Results of GitLab environment info
Expand for output related to GitLab environment info
$ sudo gitlab-rake gitlab:env:info
System information System: Proxy: no Current User: git Using RVM: no Ruby Version: 2.3.3p222 Gem Version: 2.6.6 Bundler Version:1.13.7 Rake Version: 12.0.0 Redis Version: 3.2.5 Git Version: 2.13.5 Sidekiq Version:5.0.4 Go Version: unknown
GitLab information Version: 9.5.3-ee Revision: 2edb3f1 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.3 URL: https://{DOMAIN} HTTP Clone URL: https://{DOMAIN}/some-group/some-project.git SSH Clone URL: git@${DOMAIN}:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: no
GitLab Shell Version: 5.8.0 Repository storage paths:
- default: /mnt/efs/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
$ sudo gitlab-rake gitlab:check SANITIZE=true Checking GitLab Shell ...GitLab Shell version >= 5.8.0 ? ... OK (5.8.0) 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: ... 2/4 ... repository is empty 1/6 ... repository is empty 1/7 ... repository is empty 1/8 ... repository is empty 1/10 ... repository is empty Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Access to /mnt/efs/gitlab/home/.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 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? ... skipped (no tmp uploads folder yet) 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: ... 2/4 ... yes 1/6 ... yes 1/7 ... yes 1/8 ... yes 1/10 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.3 ? ... yes (2.3.3) Git version >= 2.7.3 ? ... yes (2.13.5) Active users: ... 1 Elasticsearch version 5.1 - 5.3? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished