Error and warning messages
Import and export jobs may have associated messages after a migration is completed.
The messages range in severity from low (warnings) to high (errors), and if a job is associated with error messages, there is a chance it has not completed successfully.
Warnings
Warnings contain information that is important for the admin to consider before using an export archive or after importing archives.
Errors
A job is not considered successful if at least one error message is registered with it. More information about an error, such as the full stack trace for exceptions, is available in the server logs.
Export Warnings
Number of repositories / projects has changed since the export was
first initiated.
Meaning: Repositories may have been created, deleted, renamed or moved while the export job was executing. This has no effect on the export, except for repositories not being exported if they don't match the repository selector anymore, or projects being exported if they now match the repository selector.
Recommended action: None.
Export errors
Could not serialize object with id: '<ID>' to JSON
Meaning: An exception occurred while exporting pull request data. This means that the export archive will be missing some data related to pull requests.
Recommended action: Delete export archive and retry export.
Could not export attachments for '<ID>': an unexpected error
occurred: <MESSAGE>
Meaning: An exception occurred while exporting repository attachments. This means some attachments for the repository mentioned will be missing.
Recommended action: Delete export archive and retry export.
Exception executing callback '<METHOD>' on '<EXPORTER>':
'<MESSAGE>'
Meaning:
An exception occurred while executing a request to an exporter interface. Data Center Migrations uses a collection of exporters to migrate data. If this message is logged, some data of their related entities might be missing:
GitRepositoryExporter: Git data might be corrupt or missing. The resulting export archive will most likely contain corrupt Git data.
GitLfsSettingsExporter: The setting whether Git LFS is enabled was not exported.
MetadataExporter: Project or repository metadata, such as name, description, owner, fork hierarchy or public accessibility setting, may not have been exported correctly.
PullRequestExporter: Data related to pull requests, such as title, description, reviewers, and other activity, may not have been exported correctly.
RefSyncStatusExporter: For forked repositories that have fork synchronization enabled, the synchronization status may not have been exported correctly.
PermissionExporter: Permissions for projects or repositories may not have been exported completely.
Recommended action: Delete export archive and retry export.
Import warnings
Failed to delete file: <FILE>.
Failed to delete temp directory: <DIRECTORY>.
Following errors happened while deleting temp directory:
<ERRORS>
Meaning: During import, some temporary files and directories are created and then cleaned up. This message means that a file or directory could not be cleaned up and may have to be cleaned up manually.
Recommended action: Delete these files after import manually.
Custom hooks have been imported and stored in directory:
<DIRECTORY>.
Meaning: Git repositories on disk may contain custom hooks that an administrator has placed there manually. These hooks are not migrated as-is, but are placed in a different directory so Git does not use them.
Recommended action: To enable these custom hooks again, they have to be moved out of this directory and into the corresponding 'hooks' directory of the repository.
Unknown entry '<ENTRY>' found in archive
Meaning: This message is registered when the export archive contains an entry that the import job did not handle. This message can have a multitude of causes, and means that the data related to this entry is not imported. The most common cause is when an export archive has been tampered with.
Recommended action: Verify that repositories have been imported correctly.
Detected inconsistency with repository '<REPOSITORY>'
Meaning: Integrity checks are run on repositories after they have been imported. It is possible for these checks to find and fix inconsistencies, which are logged as warnings.
Recommended action: None.
Import errors
Could not import comment activity '<ACTIVITY>' for pull request
'<PULL REQUEST>': the referenced comment could not be found.
This may be due to an earlier import error.
Meaning: A pull request activity (such as replies to comments) is referencing a comment that could not be found. This means that some activity stream data will be missing from the mentioned pull request.
Recommended action: Check the server logs and verify that the pull request has been imported correctly.
Could not import activity '<ACTIVITY>' for pull request
'<PULL REQUEST>': an unexpected error occurred and the
activities in the current batch will be rolled back: <MESSAGE>
Meaning: A pull request activity could not be imported due to the mentioned error message. Some data related to this pull request will be missing.
Recommended action: Check the server logs and verify that the pull request has been imported correctly.
Error performing an integrity check. Further checks will continue.
Meaning: Integrity checks are run on repositories after they have been imported. It is possible for these checks to find errors that can not be fixed.
Recommended action: Check the server logs. Log messages preceding this one may give more information about why this check failed.
Checking the integrity of imported repository hierarchy
<HIERARCHY ID> failed with an unexpected error: <MESSAGE>
Meaning: Integrity checks have failed with an unexpected error.
Recommended action: Check the server logs. Log messages preceding this one may give more information about why this check failed.
Checking the integrity of imported repositories failed with
an unexpected error: <MESSAGE>
Meaning: Integrity checks have failed with an unexpected error.
Recommended action: Check the server logs. Log messages preceding this one may give more information about why this check failed.
The importing of repository '<REPOSITORY>' failed to complete:
an unexpected error occurred while attempting to make it available
to the system: <MESSAGE>
Meaning: The repository state could not be set to AVAILABLE.
Recommended action: These repositories failed to import and may have to be cleaned up manually. Delete these repositories using the REST API.
Exception executing callback '<METHOD>' on '<IMPORTER>':
'<MESSAGE>'
Meaning:
An exception occurred while executing a request to an importer interface. Data Center Migrations uses a collection of importers to migrate data. If this message is logged, some data to their related entities might be missing:
GitRepositoryImporter: Git data was not imported completely. The repository is most likely not usable and should be deleted.
GitLfsSettingsImporter: The setting whether Git LFS is enabled was not imported.
MetadataImporter: Project or repository metadata, such as name, description, owner, fork hierarchy or public accessibility setting, may not have been imported correctly.
PullRequestImporter: Data related to pull requests, such as title, description, reviewers, and other activity, may not have been imported correctly.
RefSyncStatusImporter: For forked repositories that have fork synchronization enabled, the synchronization status may not have been imported correctly.
PermissionImporter: Permissions for projects or repositories may not have been imported completely.
Recommended action: The affected repositories were most likely not imported correctly. They should be deleted using the REST API and another attempt at importing them should be made. If repeated attempts fail, it might help to export again.