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
  • #1277

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

  • Report abuse

  • New issue

  • Report abuse

"Gitlab was unable to access your Gitolite system." but gitlab:app:status shows no problem

Closed

"Gitlab was unable to access your Gitolite system." but gitlab:app:status shows no problem

Created by: danray0424

Issue is in the title. When I create my first new repo in gitlab, I get an error about not being able to reach gitolite.

When I run the status check, everything comes back good.

I've confirmed that I'm doing both of those things as the same user (named gitlab).

Linked issues
0


  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: danray0424

    Figured it out. The log showed me "C is not in the allowed list of permissions!".

    Googling that brought me to a patch for the gitolite client vendor package, here: https://github.com/wingrunr21/gitolite/commit/cb100415e7

    Evidently the client doesn't behave well with "create" permissions on wildcard or regex repo specs.

    Manually applying that patch made it work.

    By Administrator on 2012-08-23T12:32:24 (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
Assign to
Milestone
No milestone
None
None
Time tracking
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
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
participants
Reference:

Menu

Projects Groups Snippets
Help