-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Migrations - Space - Import
-
7
-
Severity 2 - Major
-
10
Issue Summary
The customer is trying to migrate a bulk number of spaces using CCMA 3.4.15 and 3.4.17, they are seeing a large number of spaces failing to migrate with this error message - 'Container did not start'. The actual problem appears to occur in bulk uploads and not in a single space upload.
Steps to Reproduce
- Launch CCMA 3.4.15 or 3.4.17
- Attempt to Migrate the bulk number of spaces; most of those spaces are failing to migrate with this error - 'Container did not start'
Expected Results
Expected all the spaces to be migrated without any problems.
Actual Results
The actual problem is occurring from import side
2023-09-27 18:27:26,101 ERROR [com.atlassian.migration-StepExecutionService:thread-19] [agent.service.stepexecutor.ProgressTracker] error Step failed, message: Import to cloud failed. Message: ERROR: new row for relation "content_perm" violates check constraint "content_perm_valid_principal_fields";
Workaround
No Workaround