GitLab 5.1: rake import brings empty project
Created by: sroth80021
Using GitLab 5.1 and following the rake import help, when I:
- place my bare repository in the repositories directory as configured in config/gitlab.yml
- run the import task -- bundle exec rake gitlab:import:repos RAILS_ENV=production
Even though the bare repository was not empty, the repository is imported as an empty repository. No error was reported by the gitlab:import:repos tool. The empty repository is confirmed when I run gitlab:check, which says the 'repository is empty'.
import command output: bundle exec rake gitlab:import:repos RAILS_ENV=production Processing a.git
- Created a (a.git) Done!
While this ran, the production log said: Connecting to database specified by database.yml Creating scope :opened. Overwriting existing method Issue.opened. Creating scope :closed. Overwriting existing method MergeRequest.closed. Rendered notify/project_access_granted_email.html.haml within layouts/notify (1.3ms) Rendered notify/project_access_granted_email.text.erb (0.3ms) Sent mail to admin@local.host (176ms)
And the sidekiq log said: 2013-04-23T20:09:35Z 7310 TID-onsc8 GitlabShellWorker JID-8622acbf78ef3b2f1d4fb837 INFO: start Initialized empty Git repository in /scratch/git/repositories/root/a.git/ 2013-04-23T20:09:35Z 7310 TID-onsc8 GitlabShellWorker JID-8622acbf78ef3b2f1d4fb837 INFO: done: 0.468 sec 2013-04-23T20:09:49Z 7310 TID-onsc8 Sidekiq::Extensions::DelayedMailer JID-50883b71e51e95f93b3a666a INFO: start 2013-04-23T20:09:49Z 7310 TID-onsc8 Sidekiq::Extensions::DelayedMailer JID-50883b71e51e95f93b3a666a INFO: done: 0.205 sec
I am able to successfully import via the browser 'new project' page, accessing a http URL. This leads me to conclude the issue is somewhere specific to the rake import call path.
Also, potentially related -- once the import of the repository has finished, I am unable to transfer it outside of the Administrator namespace -- in the browser, I get the error: 'Cannot move project' -- no error was logged in either the production log or the sidekiq log.
Activity
Created by: sroth80021
Forgot to mention -- this is a clean 5.1 install. I did not see this issue in a clean 5.0 install, which leads me to believe it is new in 5.1
$ git --version git version 1.7.1
By Administrator on 2013-04-23T22:02:18 (imported from GitLab project)
By Administrator on 2013-04-23T22:02:18 (imported from GitLab)
Created by: sroth80021
Looking in the repositories/ directory, I see the repository is empty -- git log shows fatal: bad default revision 'HEAD'
I can see the repo contents if (after doing the above) I manually copy the original bare repository directory from the repositories directory into the admin user's repository directory, then update the hooks/post-receive and hooks/update symlinks to refer to those in gitlab-shell/hooks/update.
However, I still cannot transfer the repository to the global namespace -- I still keep getting the 'Cannot move project' error, but I dont see anything problematic logged in the logfiles, so I'm not sure what is going on.
If I create a new project and use the import project from url approach to import into the admin namespace, I am able to succesfully move that project to the global namespace. So this issue I think is somehow related to the rake import process.
By Administrator on 2013-04-23T21:26:20 (imported from GitLab project)
By Administrator on 2013-04-23T21:26:20 (imported from GitLab)
Created by: sroth80021
At first, I thought this might be related to the git version, but this does not appear to be the case -- updated from 'git 1.7.1' to 'git 1.8.2' and the issue still persists.
By Administrator on 2013-04-23T22:54:03 (imported from GitLab project)
By Administrator on 2013-04-23T22:54:03 (imported from GitLab)
Created by: sroth80021
It appears this can be fixed by applying the fix from issue #3724 (closed) -- commit 2e8db0df
I added one line to lib/tasks/gitlab/import.rake: project_params = { :name => path, } becomes project_params = { :name => path, :namespace_id => Namespace.global_id, }
I think this fix needs to be rolled into the 5.1 line.
By Administrator on 2013-04-25T13:56:04 (imported from GitLab project)
By Administrator on 2013-04-25T13:56:04 (imported from GitLab)
Created by: kurevin
Confirming, reapplying commit 2e8db0df fixed the issue.
By Administrator on 2013-05-09T01:20:32 (imported from GitLab project)
By Administrator on 2013-05-09T01:20:32 (imported from GitLab)
Created by: byronsanchez
I was having the exact same issues when importing existing repos using GitLab (tagged v5.2.0).
Applying commit 2e8db0df fixed the issue for me. The only difference is that "name" is no longer a symbol, but "namespace" still is. So I ended up with:
project_params = { name: path, :namespace_id => Namespace.global_id, }By Administrator on 2013-05-24T02:32:44 (imported from GitLab project)
By Administrator on 2013-05-24T02:32:44 (imported from GitLab)
Created by: tnarik
Using:
project_params = { name: path, namespace_id: Namespace.global_id, }in
gitlab/lib/tasks/gitlab/import.rake, imports the repository to the global namespace/, and afterwards it can be moved to any user namespace.By Administrator on 2013-05-29T22:07:29 (imported from GitLab project)
By Administrator on 2013-05-29T22:07:29 (imported from GitLab)
Created by: bbodenmiller
Does this issue still exist on the latest master? Thanks for the issue report. Please reformat your issue to conform to the issue tracker guidelines found in our contributing guidelines.
By Administrator on 2013-06-15T08:25:24 (imported from GitLab project)
By Administrator on 2013-06-15T08:25:24 (imported from GitLab)
Created by: deanward81
Yes this still affects master and 5.3-stable, fix by @tnarik works.
By Administrator on 2013-06-20T09:54:46 (imported from GitLab project)
By Administrator on 2013-06-20T09:54:46 (imported from GitLab)
Created by: petergus
I have the same problem as the original poster, however i notice the import.rake file as change to
project_params = { name: name,however the the lineproject = Projects::CreateContext.new(user, project_params).executeis there. running on 5.4 branch. any fix?By Administrator on 2013-08-12T17:02:31 (imported from GitLab project)
By Administrator on 2013-08-12T17:02:31 (imported from GitLab)
Created by: fsanzv
I'm running a 5.4 fresh install and fix by @tnarik works well. (only adding namespace_id line).
By Administrator on 2013-08-21T09:39:14 (imported from GitLab project)
By Administrator on 2013-08-21T09:39:14 (imported from GitLab)
Created by: ljromero
We did a fresh 5.4 install We found impossible to import it with the rake, even with the fixes here. Always get an empty repository after a succesful import:
Processing animate.css.git 2013-08-21T10:33:39Z 7430 TID-9lgfo INFO: Sidekiq client using redis://localhost:6379 with options {:namespace=>"resque:gitlab"}
- Created animate.css (animate.css.git) Done!
When we check the repo in terminal we cant do a git command, like git log or any others. We receive this answer:
fatal: bad default revision 'HEAD'
This last try with the fix by @tnarik.
By Administrator on 2013-08-21T10:54:18 (imported from GitLab project)
By Administrator on 2013-08-21T10:54:18 (imported from GitLab)
Created by: l3iggs
I can confirm that this bug still exists (imported repos are empty) in 6.1. I can also confirm that Pull Request #5005 fixes this issue in 6.1.
By Administrator on 2013-09-24T03:50:06 (imported from GitLab project)
By Administrator on 2013-09-24T03:50:06 (imported from GitLab)
Created by: jvanbaarsen
@razer6 Can you take a look please? Thanks
By Administrator on 2014-01-10T22:44:51 (imported from GitLab project)
By Administrator on 2014-01-10T22:44:51 (imported from GitLab)
Created by: nbigaouette
I'm still hit by this issue (v6.5.1, 6f6f1588).
See also #4137 (closed).
By Administrator on 2014-01-23T19:47:42 (imported from GitLab project)
By Administrator on 2014-01-23T19:47:42 (imported from GitLab)
Created by: mpycio
I had similar problem, run import and all repositories were imported as empty. Moved all repos to a subfolder and import run correctly ( 6.5.1). So instead of repositories/repo1 I moved it to repositories/namespace/repo1 and run import, all works as expected.
By Administrator on 2014-02-24T10:19:26 (imported from GitLab project)
By Administrator on 2014-02-24T10:19:26 (imported from GitLab)
Created by: neuralsandwich
Currently hitting this issue. Have tried moving the repo into a users namespace and it also failed.
What worked for me was created a new folder (read namespace) in the repo directory and putting the file in there.
By Administrator on 2014-03-11T17:11:37 (imported from GitLab project)
By Administrator on 2014-03-11T17:11:37 (imported from GitLab)
Created by: thomasbiddle
My issue on the latest version (6.5? Will have to check) was that after copying my .git repositories into repositories/groupname/ the permissions were not set to git:git
By Administrator on 2014-03-29T15:46:46 (imported from GitLab project)
By Administrator on 2014-03-29T15:46:46 (imported from GitLab)
Created by: jvanbaarsen
@jacobvosmaer Any clues on this one?
By Administrator on 2014-03-30T10:31:56 (imported from GitLab project)
By Administrator on 2014-03-30T10:31:56 (imported from GitLab)
Created by: jacobvosmaer
The root namespace was deprecated in 6.0, so only import as
/home/git/repositories/foo/bar.git.Not sure what happens if you try to import into an existing namespace (e.g.
/home/git/repositories/myuser/bar.git).By Administrator on 2014-04-01T11:09:07 (imported from GitLab project)
By Administrator on 2014-04-01T11:09:07 (imported from GitLab)
Created by: pejvan
Same empty repositories here, with GitLab 7.0.0 (gitlab_7.0.0-omnibus-1_amd64.deb)
I tried with a non-root namespace and still had the issue
By Administrator on 2014-07-02T16:01:22 (imported from GitLab project)
By Administrator on 2014-07-02T16:01:22 (imported from GitLab)
Created by: jlnr
I ran into this issue as well, but unlike ljromero, I ended up with many empty (but valid) git repositories.
I've then deleted the projects and moved the repositories into
repositories/jlnr. Re-running the rake task gave me this error for every single repository, but it all seems to work regardless:* Failed trying to create group jlnrEdit: Hm, but I had to re-create the satellites afterwards, which were missing from all new projects.
By Administrator on 2014-08-31T22:33:47 (imported from GitLab project)
By Administrator on 2014-08-31T22:33:47 (imported from GitLab)
Created by: jacobvosmaer
During a restore, all messages from git are suppressed. Maybe something useful shows up if you replaceWrong rake task :({err: '/dev/null', out: '/dev/null'}with{}(the empty hash) before restoring.By Administrator on 2014-09-01T14:26:01 (imported from GitLab project)
By Administrator on 2014-09-01T14:26:01 (imported from GitLab)
Created by: BenKoerber
I ran into the same issue using
- Ubuntu 14.04
- GitLab 7.3.2
- GitLab Shell 2.0.1
- GitLab API v3
- Ruby 2.1.2p95
- Rails 4.1.1
- /opt/gitlab/embedded/bin/git version -> git version 2.0.0
However, I've just moved the repos to be imported into the root dir (e.g. /var/opt/gitlab/git-data/repositories/root/) and started the import using gitlab-rake gitlab:import:repos
Even though I got an error stating "Failed trying to create group root" the import worked like a charm.
Maybe this helps.
By Administrator on 2014-10-04T17:28:27 (imported from GitLab project)
By Administrator on 2014-10-04T17:28:27 (imported from GitLab)
Created by: iakovgan
I had the same issue with gitlab7. Appeared to be a rights issue that 'reconfigure' does not fix.
[root@vm ~]# cd /var/opt/gitlab/ [root@vm gitlab]# chown git:git * -RvIt may be a little brutal but works.
Then gitlab:import:repos worked fine
By Administrator on 2014-12-02T08:59:04 (imported from GitLab project)
By Administrator on 2014-12-02T08:59:04 (imported from GitLab)
Created by: jacobvosmaer
I know this does not help solve this issue but I feel obligated to point out that the solution proposed above by @iakovgan throws all file-based security in omnibus-gitlab out the window, and is likely to break a lot of things. (Will Postgres restart if
gitlab-psqldoes not own its data directory? Can Redis still right memory dump files? Etc.)That
chowncommand is a very bad idea.By Administrator on 2014-12-02T09:58:54 (imported from GitLab project)
By Administrator on 2014-12-02T09:58:54 (imported from GitLab)
