JCMA unable to start plan on Windows platform

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • 0
    • Hide

      Fixed in 1.12.15

      Show
      Fixed in 1.12.15

      Issue Summary

      When Jira is installed on Windows and errors occur in the preflight or attachment upload process, logs are unable to be written to files as they have timestamps with the colon punctuation (':') in the name, which is not permitted for filenames on Windows.

      This prevents to save a plan, as it is stuck in the pre-migration checks.

      Steps to Reproduce

      1. Install Jira Data Center on Windows
      2. Import projects from a Cloud instance
      3. Use JCMA to migrate to another Cloud site (JSM)

      Expected Results

      Errors should be able to be logged, but can't due to certain characters not permitted by Windows filesystems.

      Actual Results

      The below exception is thrown in the atlassian-jira-migration.log file:

      2024-11-26 13:09:44,341 JCMA-MigrationEventBus-pool-1-thread-4 WARN mark.klassen 789x575x2 svqql3 192.168.11.113 /rest/migration/latest/check/4cc5b69a4c5b4c1f70b5df5d9bfa0f18711cb90f [jira.migration.log.PreflightLogsService] Error executing preflight log processing
java.nio.file.InvalidPathException: Illegal char <:> at index 78: preflight-isolated-logs-4cc5b69a4c5b4c1f70b5df5d9bfa0f18711cb90f-2024-11-26T21:09:44.334Z.zip
	at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
	at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
	at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
	at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
	at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
	at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53)
	at com.atlassian.jira.migration.log.PreflightLogsService.generateMigrationIsolatedLogsZip(PreflightLogsService.kt:172)
	at com.atlassian.jira.migration.log.PreflightLogsService.uploadPreflightLogs(PreflightLogsService.kt:77)
	at com.atlassian.jira.migration.log.PreflightLogsService$onPreflightCompletionEvent$1.invoke(PreflightLogsService.kt:56)
	at com.atlassian.jira.migration.log.PreflightLogsService$onPreflightCompletionEvent$1.invoke(PreflightLogsService.kt:55)
	at com.atlassian.jira.migration.log.PreflightLogsService.runWithJiraThreadLocalUtil(PreflightLogsService.kt:154)
	at com.atlassian.jira.migration.log.PreflightLogsService.onPreflightCompletionEvent(PreflightLogsService.kt:55)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
	at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
	at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
	at com.google.common.eventbus.AsyncEventBus.access$001(AsyncEventBus.java:34)
	at com.google.common.eventbus.AsyncEventBus$1.run(AsyncEventBus.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Lavanya Rangarajan [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: