Details
-
Bug
-
Resolution: Fixed
-
Low
-
CCMA - 3.4.5, CCMA - 3.4.6
-
None
-
1
-
Minor
Description
Issue Summary
With CCMA 3.4.6, when migrating spaces and apps with the scoped user option, the migration plan will fail to start.
Steps to Reproduce
- Create a migration plan and select some spaces and scoped users option
- Add some apps to the same migration plan
- Run the migration
Expected Results
The migration will execute
Actual Results
The below exception is thrown in the atlassian-confluence.log file:
2023-05-25 00:00:00,473 ERROR [pool-77-thread-1] [agent.service.impl.DefaultPlanService] startPlan Fail to start the plan: 3d1e50a4-4b7e-4706-bd40-8b1a6bea -- referer: https://confluenceserver/admin/migration.action?& | url: /rest/migration/latest/plan/3d1e50a4-4b7e-4706-bd40-8b1a6bea/start | traceId: e2105bf0f5f | userName: user java.lang.IllegalStateException: Could not find step planning engine for task of type: com.atlassian.migration.agent.entity.MigrateAppsTask at com.atlassian.migration.agent.service.execution.PlanExecutionService.lambda$getStepPlanningEngine$16(PlanExecutionService.java:597) at java.base/java.util.Optional.orElseThrow(Unknown Source) at com.atlassian.migration.agent.service.execution.PlanExecutionService.getStepPlanningEngine(PlanExecutionService.java:597) at com.atlassian.migration.agent.service.execution.PlanExecutionService.generateNextStep(PlanExecutionService.java:508) at com.atlassian.migration.agent.service.execution.PlanExecutionService.generateNextStep(PlanExecutionService.java:492) at java.base/java.util.ArrayList.forEach(Unknown Source) at com.atlassian.migration.agent.service.execution.PlanExecutionService.lambda$runPlan$1(PlanExecutionService.java:248) at com.atlassian.migration.agent.store.jpa.impl.DefaultPluginTransactionTemplate.on(DefaultPluginTransactionTemplate.java:36) at com.atlassian.migration.agent.store.tx.PluginTransactionTemplate.write(PluginTransactionTemplate.java:24) at com.atlassian.migration.agent.service.execution.PlanExecutionService.runPlan(PlanExecutionService.java:243) at com.atlassian.migration.agent.service.impl.DefaultPlanService.startPlan(DefaultPlanService.java:394) at com.atlassian.migration.agent.service.impl.PlanDecoratorService.startPreflightCheckAndPoll(PlanDecoratorService.java:213) at com.atlassian.migration.agent.service.impl.PlanDecoratorService.startPreflightChecksAndPoll(PlanDecoratorService.java:183) at com.atlassian.migration.agent.service.impl.PlanDecoratorService.lambda$verifyAndStart$0(PlanDecoratorService.java:154) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)
Workaround
Enable the below Dark Feature to disable scheduler fixes:
- migration-assistant.disable.scheduler.fixes