The import status remains in `started` indefinitely for mirrored GitHub repositories

Summary

One of our customers reported that the pull mirrors from GitHub are not updating. The mirror status shows last successful update NEVER and the API shows its "import_status":"started".

Based on the discussion happened on the internal issue (#116), it looks like the GithubImport job gets stuck in started status for some reason.

Internal Logs : Kibana Logs

Steps to reproduce

1. Check for the API response for import status of the mirrored project and it will remain in started state, indefinitely.

Example Project

• Internal link – Link

What is the current bug behavior?

• The import status remains in started indefinitely

What is the expected correct behavior?

• The import should complete

Relevant logs and/or screenshots

Output of checks

/label reproduced on GitLab.com

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

Workaround

1. As a workaround, "delete existing pull mirroring settings, then recreate them via mirroring configuration page" should help.
2. Wait 24 hours for the import to timeout with error Import timed out. Import took longer than 86400 seconds. Click Update Now and mirroring should start to sync again.