Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1016

JSM project export fails with error "com.atlassian.jira.migration.orchestratorclient.OrchestratorClientErrorException: request to Migration Orchestrator failed"

    XMLWordPrintable

Details

    • 17
    • Minor

    Description

      Issue Summary

      When migrating JSM projects via JCMA, Project migration will fail at 0%, error logs aren't generated and the following error message is displayed in the GUI

      "com.atlassian.jira.migration.orchestratorclient.OrchestratorClientErrorException: request to Migration Orchestrator failed"

      Currently this issue isn't reproducible.

      Steps to Reproduce

      todo

      Expected Results

      Project should migrate successfully.

      Actual Results

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

      2022-03-23 17:30:11,985 pool-33-thread-6 ERROR      [c.a.j.m.tracking.polling.Poller] xxxaba49-9797-xxxx-xx-129xxxxxxxcx-projectDataUpload#ABCD$...31d1...: task worker 26f7aa...982f failed to process Task(migrationId=8d4....4, migrationTask=com.atlassian.jira.migration.orchestratorclient.tasks.ProjectDataUpload@5af.....[projectKey=ABCD,migrationTaskType=projectDataUpload,taskId=projectDataUpload#ABCD$5.....529], cloudSite=AO_6FF49D_CLOUD_SITE {CLOUD_ID =.......})com.atlassian.jira.migration.orchestratorclient.OrchestratorServerErrorException: failed to send a request to server        at com.atlassian.jira.migration.orchestratorclient.OrchestratorExceptions.serverError(OrchestratorExceptions.kt:39)        at com.atlassian.jira.migration.orchestratorclient.MigrationOrchestratorClient.toMOException(MigrationOrchestratorClient.kt:456)        at com.atlassian.jira.migration.orchestratorclient.MigrationOrchestratorClient.execute(MigrationOrchestratorClient.kt:432)        at com.atlassian.jira.migration.orchestratorclient.MigrationOrchestratorClient.execute(MigrationOrchestratorClient.kt:423)        at com.atlassian.jira.migration.orchestratorclient.MigrationOrchestratorClient.uploadFileToURL(MigrationOrchestratorClient.kt:286)        at com.atlassian.jira.migration.workers.ProjectProcessor$process$2$1.invoke(ProjectsWorker.kt:163)        at com.atlassian.jira.migration.workers.ProjectProcessor$process$2$1.invoke(ProjectsWorker.kt:162)        at com.atlassian.jira.migration.tracking.tasks.OperationProcessor$runTimedOperation$1.invoke(OperationProcessor.kt:36)        at com.atlassian.jira.migration.tracking.tasks.OperationProcessor$runTimedOperation$1.invoke(OperationProcessor.kt:35)        at com.atlassian.jira.migration.tracking.tasks.OperationProcessor$runTimedOperationWithResult$1.invoke(OperationProcessor.kt:52)        at com.atlassian.jira.migration.events.JiraEventDetectionService.runAndDetect(JiraEventDetectionService.kt:69)        at com.atlassian.jira.migration.tracking.tasks.OperationProcessor.runTimedOperationWithResult(OperationProcessor.kt:49)        at com.atlassian.jira.migration.tracking.tasks.OperationProcessor.runTimedOperation(OperationProcessor.kt:35)        at com.atlassian.jira.migration.workers.ProjectProcessor.process(ProjectsWorker.kt:162)        at com.atlassian.jira.migration.workers.ProjectsWorker.process(ProjectsWorker.kt:83)        at com.atlassian.jira.migration.tracking.polling.Poller.dispatchTask(Poller.kt:116)        at com.atlassian.jira.migration.tracking.polling.Poller.pollForTaskAndDispatch(Poller.kt:111)        at com.atlassian.jira.migration.tracking.polling.Poller.pollForTaskAndDispatchNoThrow(Poller.kt:65)        at com.atlassian.jira.migration.tracking.polling.Poller.doPoll(Poller.kt:50)        at com.atlassian.jira.migration.tracking.polling.AbstractPoller.execute(AbstractPoller.kt:62)        at com.atlassian.jira.migration.tracking.polling.AbstractPoller.access$execute(AbstractPoller.kt:16)        at com.atlassian.jira.migration.tracking.polling.AbstractPoller$startPolling$1.invoke(AbstractPoller.kt:35)        at com.atlassian.jira.migration.tracking.polling.AbstractPoller$startPolling$1.invoke(AbstractPoller.kt:35)        at com.atlassian.jira.migration.tracking.utils.ThreadUtils.safeExecutePeriodicallyUntilStopped(ThreadUtils.kt:43)        at com.atlassian.jira.migration.tracking.polling.AbstractPoller.startPolling(AbstractPoller.kt:34)        at com.atlassian.jira.migration.tracking.MigrationTracker.addAndStartWorkPoller$lambda-4$lambda-3(MigrationTracker.kt:78)        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)        at java.util.concurrent.FutureTask.run(FutureTask.java:266)        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)Caused by: com.atlassian.jira.migration.httpclient.exceptions.HttpCommunicationException: An error occurred when requesting against resource https://....s3.us.....amazonaws.com/migrations/.../projects/ABCD/project-export?X-Amz-...=...: Connection reset by peer: socket write error        at com.atlassian.jira.migration.httpclient.exceptions.ExceptionsKt.communicationError(Exceptions.kt:13)        at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.execute(AbstractPluginHttpClient.kt:76)        at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.execute(AbstractPluginHttpClient.kt:51)        at com.atlassian.jira.migration.orchestratorclient.MigrationOrchestratorClient.execute(MigrationOrchestratorClient.kt:430)        ... 28 more 

      Workaround

      Not identified

      Attachments

        Issue Links

          Activity

            People

              c52a2cdc2848 Viktor Semenyuk
              cb409c559c8f Keith Pinto (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: