Help with a possible repository import bug?

We have a self-hosted GitLab CE 9.4 on Centos 7.3 that we’re trying to migrate to gitlab.com. I used the project export feature to produce an archive of one of our repositories. I have a brand new group in gitlab.com and used the import project option.

The importer works for a bit, the screen changes, refreshes, and then…

The repository could not be imported.

Error importing repository into example/example - tar (child): [REPO EXPORT PATH]/uploads/201e8b880a0c7a633d048386638ea634_example: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
, undefined method `join' for nil:NilClass
Did you mean? JSON

I can’t tell if the problem is with the GitLab-produced export archive (the “cannot open” part of the error message). I can browse the archive using the normal tools and it seems to be OK.

$ tar --list --gzip --file example_export.tar.gz  --verbose
drwx------ git/git           0 2017-09-19 10:25 ./
-rw-r--r-- git/git           5 2017-09-19 10:25 ./VERSION
-rw-r--r-- git/git    27014627 2017-09-19 10:25 ./project.json
drwx------ git/git           0 2017-09-19 10:25 ./uploads/
drwxr-xr-x git/git           0 2017-09-19 10:25 ./uploads/ce4520bd81d88cdcf40931111e1e2d85/
-rw-r--r-- git/git      161315 2017-09-19 10:25 ./uploads/ce4520bd81d88cdcf40931111e1e2d85/image.png
drwxr-xr-x git/git           0 2017-09-19 10:25 ./uploads/5919450566358aefeb7fa9b4bdfdc906/
-rw-r--r-- git/git      218495 2017-09-19 10:25 ./uploads/5919450566358aefeb7fa9b4bdfdc906/foo.PNG
drwxr-xr-x git/git           0 2017-09-19 10:25 ./uploads/620365634fb314c41486ca36216dbfc6/
-rw-r--r-- git/git      123328 2017-09-19 10:25 ./uploads/620365634fb314c41486ca36216dbfc6/bar.PNG
-rw-r--r-- git/git    13545568 2017-09-19 10:25 ./project.bundle

Or, is the problem in the Ruby code for the importer (the undefined method part of the error).

So, I’m not sure if I just need sysadmin troubleshooting help or if I need to file a bug.

Oh, my search abilities are growing… I found a possible pre-existing, but very recent, bug.

And the bug is fixed… case closed :slight_smile: