-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: JCMA - 1.12.28, JCMA - 1.12.30, JCMA - 1.12.31, JCMA - 1.12.32, JCMA - 1.12.33, JCMA - 1.12.34
-
Component/s: Viper CMAs - Australia
-
None
-
2
-
Severity 3 - Minor
-
11
Issue Summary
Selecting to "Remove x projects from migration" in the pre-migration screen may not actually remove projects from the plan. This may also cause execution errors in running the checks.
Steps to Reproduce
- Attempt to migrate a project that already exists in cloud
- Select to "Remove x projects from migration" in the pre-migration checks screen
Or
- Attempt to migrate a project that is affected by project export error
- Select to "Remove x projects from migration" in the pre-migration checks screen
Expected Results
The projects are removed from the migration plan and new pre-migration checks run.
Actual Results
New pre-migration checks run but the plan is not changed to remove the selected projects.
Further, the data preparation check may start fail to execute correctly and the following error can be observed in the log file:
2025-05-06 15:26:25,728 JCMA-JCMAExecutorService-pool-1-thread-55 WARN admin 926x1691x1 1erf22e 0:0:0:0:0:0:0:1 /rest/migration/latest/check/45ec794cd6e85bab0ecf2027dcec3f509264f168 [jira.migration.preflight.PreflightService] (DraftPreflight:45ec794cd6e85bab0ecf2027dcec3f509264f168) check execution 45ec794cd6e85bab0ecf2027dcec3f509264f168 - d2cb0d57-ff0e-4a30-90c8-3e8d58c34347 failedjava.lang.IllegalStateException: PlanId not found for preflightId: d2cb0d57-ff0e-4a30-90c8-3e8d58c34347 and executionId: 45ec794cd6e85bab0ecf2027dcec3f509264f168 at com.atlassian.jira.migration.preflight.dryrun.MultiNodeDryRunPreflightService.findPlanId(MultiNodeDryRunPreflightService.kt:117) at com.atlassian.jira.migration.preflight.dryrun.MultiNodeDryRunPreflightService.performCheck(MultiNodeDryRunPreflightService.kt:44) at com.atlassian.jira.migration.preflight.dryrun.ProjectReportErrorCheck.performCheck(ProjectReportErrorCheck.kt:77) at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.runCheck$lambda$20(AsyncCheckExecutor.kt:451) at io.prometheus.metrics.core.datapoints.TimerApi.time(TimerApi.java:71) at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.runCheck(AsyncCheckExecutor.kt:450) at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.executeChecksListenable$lambda$18$lambda$16$lambda$15$lambda$13(AsyncCheckExecutor.kt:290) at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125) at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57) at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at com.atlassian.jira.migration.thread.MDCAwareRunnable.run(MDCAwareGroupedThreadFactory.kt:48) at java.base/java.lang.Thread.run(Thread.java:840)
Workaround
Edit the migration plan to manually remove any projects that you no longer wish to migrate at this time and re-run the pre-migration checks.
- mentioned in
-
Page Loading...