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

Closed
Open
Created Jan 15, 2015 by Administrator@rootOwner

Could not read from remote repository.

Created by: offlinehoster

Hi,

every few days we have this "Could not read from remote repository." issue after create a new repo and try to clone/push this repo.

1.) User is creating a new private project called "example" with access for group "Employees" 2.) User is trying to clone this repo 3.) Error "Could not read from remote repository." appears on the user shell 4.) deleting project "example" by gitlab webinterface 5.) re-creating the project "example" 6.) User is trying to clone this repo again 7.) Error "Could not read from remote repository." appears on the user shell 8.) the admin, me, is deleting the repo "example" by gitlab webinterface 9.) the admin, me, is deleting the remaining files for this repo "example" on the filesystem by shell 10.) the admin, me, is doing "gitlab-rake gitlab:shell:setup" and "gitlab-ctl restart" 11.) the user can now create the repo "example" again and have access to this repo and can clone/push everything to this repo.

We're running the following version:

  • GitLab 7.5.1
  • GitLab Shell 2.2.0
  • GitLab API v3
  • Ruby 2.1.4p265
  • Rails 4.1.1
Assignee
Assign to
Time tracking