Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
JCMA - 1.7.3
-
None
-
6
-
Severity 3 - Minor
Description
Issue Summary
This is reproducible on Data Center: (yes)
JCMA will run throw exception when user selects BACK after running preflight checks. The exceptions may impact project reports generated by JCMA.
Steps to Reproduce
- JCMA v1.7.3
- Create migration plan, run checks
- Interrupt the checks or allow the checks to complete, select BACK
- Create a NEW plan with new name
- run checks for the new plan
Expected Results
The new migration plan should continue without issue
Actual Results
JCMA will run into the following error:
The below exception is thrown in the xxxxxxx.log file:
2022-09-30 14:37:16,508+0000 pool-37-thread-15 ERROR admin 876x391x1 1b91o5v 172.29.224.179,172.50.0.2 /rest/migration/latest/check/e14dd35395d8eaa7e52b0b1b658e81f064eb2e4b [c.a.j.migration.preflight.ProjectReportErrorService] Can't find project logs folder, Execution ID d118b9cb038e69db43934b45519efa4ab89b8371 java.nio.file.NoSuchFileException: /var/atlassian/application-data/jira/export/migration-to-cloud/d118b9cb038e69db43934b45519efa4ab89b8371/log/export at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) at java.base/sun.nio.fs.UnixFileSystemProvider.newDirectoryStream(UnixFileSystemProvider.java:432) at java.base/java.nio.file.Files.newDirectoryStream(Files.java:540) at kotlin.io.path.PathsKt__PathUtilsKt.listDirectoryEntries(PathUtils.kt:398) at com.atlassian.jira.migration.log.MigrationLogsService.deleteExistingPreflightExecutionProjectLogs(MigrationLogsService.kt:344) at com.atlassian.jira.migration.preflight.ProjectReportErrorService.performCheck(ProjectReportErrorService.kt:18) at com.atlassian.jira.migration.preflight.ProjectReportErrorCheck.performCheck(ProjectReportErrorCheck.kt:36) at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.runCheck(AsyncCheckExecutor.kt:182) at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.executeChecksListenable$lambda-14$lambda-12$lambda-10(AsyncCheckExecutor.kt:105) at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131) at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:74) at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)
In testing, all future migration plans will fail with the same exception for all new IDs generated. It does not appear that the error is impacting the migration, but the impact may be toward JCMA project error logs as the directory does not appear to get created properly.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available