-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Cloud to Cloud Migrations - Jira
-
None
-
Severity 3 - Minor
Issue Summary
| Error occurred when migrating container entity | com.atlassian.migration.jira.MigrationException: Expect 1 list but got 2 |
Steps to Reproduce
MigrationID : 1b0f95eb-1202-4024-a04f-d58b695a1906
Expected Results
Migration should be successful
Actual Results
The below exception is thrown in the xxxxxxx.log file:
com.atlassian.migration.jira.MigrationException: Expect 1 list but got 2 at com.atlassian.migration.jira.executor.monolith.ContainerEntityService.migrate(ContainerEntityService.kt:41) at com.atlassian.migration.jira.classic.JiraClassicCoreExecutor.executeEntities(JiraClassicCoreExecutor.kt:71) at com.atlassian.migration.jira.executor.AbstractExecutor.execute(AbstractExecutor.kt:24) at com.atlassian.migration.jira.service.batch.BatchExecutor.execute(BatchExecutor.kt:26) at com.atlassian.migration.jira.service.orchestration.Orchestrator.dispatch(Orchestrator.kt:200) at com.atlassian.migration.jira.service.orchestration.Orchestrator.doMigrate(Orchestrator.kt:155) at com.atlassian.migration.jira.service.orchestration.Orchestrator$performSequentialMigration$1$$special$$inlined$forEach$lambda$1.run(Orchestrator.kt:119) at io.micrometer.core.instrument.AbstractTimer.record(AbstractTimer.java:160) at com.atlassian.migration.jira.service.orchestration.Orchestrator$performSequentialMigration$1.run(Orchestrator.kt:106) at io.micrometer.core.instrument.AbstractTimer.record(AbstractTimer.java:160) at com.atlassian.migration.jira.service.orchestration.Orchestrator.performSequentialMigration(Orchestrator.kt:81) at com.atlassian.migration.jira.service.DispatcherService.migrate(DispatcherService.kt:53) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer$process$1.invoke(PreprocessedEntitiesConsumer.kt:42) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer$process$1.invoke(PreprocessedEntitiesConsumer.kt:19) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer$validateProjectMetaDataAndExecute$$inlined$let$lambda$1.invoke(PreprocessedEntitiesConsumer.kt:51) at com.atlassian.migration.jira.logging.LoggingContextKt.populateMdcAndInvokeFunction(LoggingContext.kt:61) at com.atlassian.migration.jira.logging.LoggingContextKt.withMigrationContext(LoggingContext.kt:54) at com.atlassian.migration.jira.logging.LoggingContextKt.withMigrationContext$default(LoggingContext.kt:43) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer.validateProjectMetaDataAndExecute(PreprocessedEntitiesConsumer.kt:50) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer.process(PreprocessedEntitiesConsumer.kt:40) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer$receiveMessage$1.invoke(PreprocessedEntitiesConsumer.kt:30) at com.atlassian.migration.jira.service.preprocessing.PreprocessedEntitiesConsumer$receiveMessage$1.invoke(PreprocessedEntitiesConsumer.kt:19) at com.atlassian.migration.jira.aws.sqs.MigrationSqsFifoClient$consume$1$1.invoke(MigrationSqsFifoClient.kt:93) at com.atlassian.migration.jira.logging.LoggingContextKt.populateMdcAndInvokeFunction(LoggingContext.kt:61) at com.atlassian.migration.jira.logging.LoggingContextKt.withMigrationContext(LoggingContext.kt:54) at com.atlassian.migration.jira.logging.LoggingContextKt.withMigrationContext$default(LoggingContext.kt:43) at com.atlassian.migration.jira.logging.LoggingContextKt.withMigrationContext(LoggingContext.kt:25) at com.atlassian.migration.jira.aws.sqs.MigrationSqsFifoClient$consume$1.run(MigrationSqsFifoClient.kt:90) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available