Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #1798

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Repository not created on disk although interface says "Project was successfully created"

Closed

Repository not created on disk although interface says "Project was successfully created"

Created by: pravincar

I've just installed gitlab on Ubuntu 12.04 following the instructions on the wiki. The database I'm using is Postgres compiled from source.

When I create a project in the web interface, although it gets created and shows up on subsequent login, the repo.git file does not appear in the git/repositories folder.

All the check were ok and the web application runs perfectly. I am able to create projects, users, add keys etc.

In order to test if gitolite was working, I've cloned the gitolite-admin repo and added a new repository to gitolite.conf. On pushing to the server, the new repo was created.

There is no error in the application or production log. Any ideas of what the issue could be and ways to trace this?

The permissions of the repositories folder are as follows:

drwxrwxr-x 5 git git 4096 Oct 25 12:04 repositories

Linked issues
0


  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: SaitoWu

    please checkout this gist: https://gist.github.com/3946188 and the comment.

    By Administrator on 2012-10-25T07:13:40 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: pravincar

    I am using the latest forked version of gitolite (3.04) and the gitolite.rc file seems to be as you have noted.

    %RC = ( # if you're using mirroring, you need a hostname. This is one simple # word, not a full domain name. See documentation if in doubt # HOSTNAME => 'darkstar', UMASK => 0007, GIT_CONFIG_KEYS => '.*',

    By Administrator on 2012-10-25T07:49:20 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: pravincar

    Have created a repository in the frontend and checked the gitolite log file. Gitolite does not create a new repo. Could there be some problem with the setup of hooks?

    Log file attached below:

    http://gidaindia.com/gitolite-2012-10.log

    By Administrator on 2012-10-25T08:07:27 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: mitrpaka

    Also having the very same issue with my Centos 6.3 box ... Using forked version of Gitolite (3.04).

    In addition to @pravincar comments I noticed that gitolite writes only following to its conf file (i.e. RW permissions not defined for new repo at all)

    repo    gitolite-admin
      RW+                            = gitlab
    repo    testing
      RW+                            = @all
    repo    test123
      config core.sharedRepository = 0660

    Any idea whether this is permission or hook related issues?

    By Administrator on 2012-10-29T08:31:35 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: pravincar

    Noticed the same thing as @mitrpaka . This happens if you have created a repo with the admin userid. Try creating a new user and then create a repo. Then gitlab writes the permission also. I'm going to redo the setup on a fresh VM all over again and hope it works!

    By Administrator on 2012-10-29T09:05:27 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: Philzen

    That's the deciding hint @pravincar, thx a lot.

    Running gitlab 3.0.3 with gitolite 3.0.4 on Gentoo and i can confirm that this does not happen when i don't create the project using any 'new project' link in the admin section.

    I was able to destroy the broken project and then created it successfully using the "+ project" link at the top menu in normal browsing mode.

    By Administrator on 2012-11-08T19:18:14 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: pravincar

    Did a fresh install with the revised instructions. Seems to be resolved!

    By Administrator on 2012-12-11T15:59:14 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
None
Assign to
Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
1
1 participant
user avatar
Reference: gpt/large_projects/gitlabhq1#1798

Menu

Projects Groups Snippets
Help