Direct Transfer - api/v4/groups/<group_name>/export_relations/status Not Found Error

Summary

I tried to migrate our company's codebase from gitlab.com to our self-hosted gitlab server. But it gives "Unsuccessful response 404 from /api/v4/groups/<group_name>/export_relations/status. Body: {"message"=>"404 Not Found"}" error.

Steps to reproduce

It is important that you try to migrate from gitlab.com to self-managed gitlab instance since it works for the migration between self-managed gitlab instances.

  1. Open destination gitlab instance.
  2. From search, go to your work.
  3. Select groups.
  4. Select new group.
  5. Select import group.
  6. Fill the info in the "Import groups by direct transfer" section.
  7. Select the target group then click import with projects or import without projects.
  8. The status will be "fail".
  9. After clicking re-import the error will be "Unsuccessful response 404 from /api/v4/groups/<group_name>/export_relations/status. Body: {"message"=>"404 Not Found"}".

Example Project

What is the current bug behavior?

The bug is the error response which is "Unsuccessful response 404 from /api/v4/groups/<group_name>/export_relations/status. Body: {"message"=>"404 Not Found"}".

What is the expected correct behavior?

The expected behavior is starting the migration process.

Relevant logs and/or screenshots

image

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes