-
Type:
Bug
-
Resolution: Tracked Elsewhere
-
Priority:
Medium
-
None
-
Affects Version/s: JCMA - 1.7.3
-
None
-
3
-
Severity 3 - Minor
Issue Summary
When a user is performing a migration there is a user-sync-delay that causes the migration to fail with messages similar to this:
2022-10-13 00:19:26.586245 ERROR XXXXX project-import We couldn't import Filter 'Filter for Board'. Reason: Could not resolve a user with the provided AAID: aaaaaaaaaaaaaaaa11111111aaaaaaaaaa
OR
2022-10-13 00:19:27.249541 ERROR XXXXX project-import We couldn't import Project Role 'role'. Reason: IllegalArgumentException: Role actor [ProjectRoleActor{id='aaaaaaaaaaaaaaaa11111111aaaaaaaaaa'}] does not exist. This caused 9999 other items to fail.
This is reproducible on Data Center: yes
Steps to Reproduce
- Generate a Server to Cloud migration with 500+ users, 50+ Projects with Boards and Saved Filters.
- Select a Cloud site that does not have any users.
- Choose to migrate all data and all projects.
Expected Results
Migration is complete with sucess.
Actual Results
The migration fails with the previously mentioned errors.
Workaround
Perform a migration with only users and groups first, and then perform a new migration with the Projects and all settings.
- derived from
-
MIG-1159 Project migration using JCMA fails with error project-import We couldn't import Issue ABCB-X. Reason: assignee: Specify a valid value for assignee. This caused 23 other items to fail.
-
- Closed
-