Details
-
Bug
-
Resolution: Fixed
-
High
-
CCMA - 3.4.3
-
None
-
6
-
Severity 3 - Minor
-
11
Description
Issue Summary
When migrating a space using Confluence CCMA v3.4.3, an error is thrown.
After completing the export, ~86% of migration, an error message is thrown in the CCMA UI:
Import to cloud failed. Message: the nameMapping array and the sourceList should be the same size (nameMapping length = 4, sourceList size = 19)
This is reproducible on Data Center: N/A
Steps to Reproduce
Intermittent
- CCMA v3.4.3
- Fixed by rolling back to v3.3.13
Expected Results
Space successfully migrates
Actual Results
Space does not migrate
The below exception is thrown in the atlassian-confluence.log file:
Import to cloud failed. Message: the nameMapping array and the sourceList should be the same size (nameMapping length = 4, sourceList size = 19)
sourceList size <number> will vary
com.atlassian.confluence.importexport.v2.ImportExportException: org.supercsv.exception.SuperCsvException: the nameMapping array and the sourceList should be the same size (nameMapping length = 4, sourceList size = 6) context=null com.atlassian.confluence.importexport.v2.ImportProcessor.processFileImport(ImportProcessor.java:383) com.atlassian.confluence.importexport.v2.ImportProcessor.lambda$doImport$2(ImportProcessor.java:281) com.atlassian.confluence.importexport.v2.csv.ImportCsvDataExtractorSimple.extract(ImportCsvDataExtractorSimple.java:77) com.atlassian.confluence.importexport.v2.ImportProcessor.doImport(ImportProcessor.java:279) com.atlassian.confluence.importexport.v2.ImportProcessor.lambda$runImportTransaction$1(ImportProcessor.java:229) org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)
Workaround
- Disable csv export
- For PostgreSQL, add dark feature migration-assistant.enable.original-xml-export
- For other database implementations, remove dark feature migration-assistant.enable.new-space-export
- Rollback to version without csv export, e.g. CCMA v3.3.13