### Summary For an unknown reason, the group and owner of the folder /var/opt/gitlab/gitlab-rails/shared/registry/docker/ where wrong (git:git instead of registry:registry). the chef client should check for the right permissions in the folder and fix them, if required (based on the user/group config parameter) ### Steps to reproduce Check the permissions of /var/opt/gitlab/gitlab-rails/shared/registry/docker/ ### Example Project --- not possible ### What is the current *bug* behavior? pushing into the registry fails with error 500, looking in the logs showing a permission denied for mkdir ### What is the expected *correct* behavior? it should "just work". :) No, but chef should check for the right permissions for the registry component and fix them if required. ### Relevant logs and/or screenshots 2017-12-13_10:56:41.03914 time="2017-12-13T11:56:41.038779079+01:00" level=error msg="response completed with error" auth.user.name=xxx environment=production err.code=unknown err.detail="filesystem: mkdir /var/opt/gitlab/gitlab-rails/shared/registry/docker/registry/v2/repositories/aaa/bbb-ccc/_uploads/zxc: permission denied" err.message="unknown error" go.version=go1.8.1 http.request.host=xxx http.request.id=903ef2b0-1571-4151-b51c-a8795db2fba1 http.request.method=POST http.request.remoteaddr=xxx http.request.uri="/v2/xxx" http.request.useragent="docker/1.13.1 go/go1.7.4 git-commit/092cba3 kernel/4.10.0-40-generic os/linux arch/amd64 UpstreamClient(Docker-Client/1.13.1 \\(linux\\))" http.response.contenttype="application/json; charset=utf-8" http.response.duration=1.698391ms http.response.status=500 http.response.written=289 instance.id=ef8430c9-3a15-4439-a849-733bc59a6c51 service=registry vars.name="xxx" version=v2.6.1-1-gdd544a8 ### Output of checks (If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com) #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> ystem information System: CentOS 7.4.1708 Current User: git Using RVM: no Ruby Version: 2.3.5p376 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.1.0 Redis Version: 3.2.5 Git Version: 2.13.6 Sidekiq Version:5.0.4 Go Version: unknown GitLab information Version: 10.2.1 Revision: eb2643f Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://xxx HTTP Clone URL: https://xxx/some-group/some-project.git SSH Clone URL: git@xxx:some-group/some-project.git Using LDAP: yes Using Omniauth: no GitLab Shell Version: 5.9.4 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> Checking GitLab Shell ... GitLab Shell version >= 5.9.4 ? ... OK (5.9.4) 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: ... 26/2 ... repository is empty 6/3 ... ok 10/4 ... ok 10/5 ... ok 37/6 ... ok 42/7 ... ok 42/8 ... ok 42/9 ... ok 11/10 ... ok 42/11 ... ok 14/12 ... repository is empty 14/13 ... repository is empty 14/14 ... repository is empty 14/15 ... repository is empty 14/16 ... repository is empty 14/17 ... repository is empty 14/18 ... repository is empty 14/19 ... repository is empty 14/20 ... repository is empty 14/21 ... repository is empty 14/22 ... repository is empty 14/23 ... repository is empty 14/24 ... repository is empty 14/25 ... repository is empty 14/26 ... repository is empty 14/27 ... repository is empty 14/28 ... repository is empty 14/29 ... repository is empty 14/30 ... repository is empty 7/31 ... ok 7/32 ... ok 43/33 ... ok 40/34 ... ok 14/35 ... repository is empty 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: ldapwecloud not verifying SSL hostname of LDAPS server 'xxx:636' LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) *** 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: ... 26/2 ... yes 6/3 ... yes 10/4 ... yes 10/5 ... yes 37/6 ... yes 42/7 ... yes 42/8 ... yes 42/9 ... yes 11/10 ... yes 42/11 ... yes 14/12 ... yes 14/13 ... yes 14/14 ... yes 14/15 ... yes 14/16 ... yes 14/17 ... yes 14/18 ... yes 14/19 ... yes 14/20 ... yes 14/21 ... yes 14/22 ... yes 14/23 ... yes 14/24 ... yes 14/25 ... yes 14/26 ... yes 14/27 ... yes 14/28 ... yes 14/29 ... yes 14/30 ... yes 7/31 ... yes 7/32 ... yes 43/33 ... yes 40/34 ... yes 14/35 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.3.5) Git version >= 2.7.3 ? ... yes (2.13.6) Git user has default SSH configuration? ... yes Active users: ... 40 Checking GitLab ... Finished </pre> </details> ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)