Using DC Migration tool with "Create New Repos in Mesh" turned on creates empty repo

Issue Summary

When attempting to migrate a repo using the DC Migration tool, doing so into a Bitbucket instance using mesh with "Create new repositories on Mesh" enabled, will not work as expected.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Have Mesh nodes installed and connected to the destination Bitbucket instance.
2. Export a repository using the above tool
3. In the destination instance, navigate to "Bitbucket Mesh"
4. Ensure "Create new repositories on Mesh" is checked.

Expected Results

The repository is imported successfully.

Actual Results

The repository is created as expected, but shows the "You have an empty repository page"

The following can be seen in the atlassian-mesh.log:

Consistency verification completed. All replicas are consistent at {content-hash=
0000000000000000000000000000000000000000000000000000000000000000, version=2}

Repositories with forks do not seem to be affected when importing.

Additional Notes:

The repository is created locally on disk in the BITBUCKET_HOME/shared/data/repositories directory with no configuration file or reference in the database. This leaves "orphaned repos" that aren't detected by Bitbucket nor the integrity checker tool. The repository will need to be manually removed and repeated attempts to import could flood the disk space.

Workaround

• Delete the empty repo created by the failed import
  (in the Bitbucket UI, go to: Repository settings > Repository details then from the "Manage repository" dropdown, select "Delete")
• Disable "Create New repositories on Mesh" in the Administration > Bitbucket Mesh page
• Re-attempt the import