Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6348

Closed
Open
Created Feb 18, 2014 by Administrator@rootOwner

New project does not create new repo

Created by: hugelgupf

Please note that this does not seem to be a duplicate of issue #3520 (closed).

Gitlab 6.5.1 / Gitlab-shell 1.8.0, with existing repos from an older installation. Git commit is the latest 6-5-stable: 2ffa03ab

When creating a new project, only the wiki-git-repo is created. Since that one is created, it must not be a permissions issue. I replaced gitlab-shell/bin/gitlab-projects with a shell that logs any call to that script and the output of id (and it redirects to the real gitlab-projects)

This is the output:

add-project ckoch/tttt.wiki.git
uid=104(git) gid=108(git) groups=108(git)
add-project ckoch/ggggg.wiki.git
uid=104(git) gid=108(git) groups=108(git)

So, gitlab does not even call upon gitlab-shell/-projects to create the repository. Why is that?

gitlab:check output: https://clbin.com/fn752


Update: I've been debugging for a while. Even though gitlab:check reports that everything is okay, I suspect that Gitlab <-> Sidekiq is having issues. I've been reading the source and I noticed that the Wiki repository is created without using Sidekiq, while both syncing authorized_keys and creating the actual repo are Sidekiq tasks. Sidekiq is running on the system, gitlab:check reports that everything is okay, and the sidekiq.log has nothing usable in it, even if I add "-v" (--verbose) to the start of sidekiq with script/background_jobs. Very curious.

Assignee
Assign to
Time tracking