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

JCMA preflight checks for Advanced Roadmaps fail with an error.

    • 10
    • Severity 2 - Major

      Issue Summary

      When creating a migration plan in JCMA, the preflight checks for Advanced Roadmaps grey out with the below text. Refer attached screenshot.

      We couldn't check If issue sources have already been migrated
      

      When this happens Run button greys out and cannot proceed with the migration. The below error is logged in the atlassian-jira.log

      Caused by: java.lang.IllegalStateException: Incorrect usage of JIRA/lucene search API. You can only create/use: ManagedIndexSearcher inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtils for details.
      

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Add the dark FF: com.atlassian.jira.migration.skip.preflight.check.export.errors
      2. Create a migration plan with the Advanced Roadmaps and more than 200+ ARs are included in the migration
      3. Select Only users and groups related to the selected projects
      4. Click on 'Check for errors' to start the pre-flight checks

      Expected Results

      The pre-flight checks should complete without any errors as they do with earlier versions.

      Actual Results

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

      2022-10-17 13:21:35,334+0200 pool-32-thread-15 ERROR 801x11843x2 1gkf8ym 10.23.133.177,10.202.0.1 /rest/migration/latest/check/62882e7027f140d9ff9ead7edd84e4a837cd3efb [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight execution error occurred for check type AdvancedRoadmapsProjectMigratedConflict
      java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Incorrect usage of JIRA/lucene search API. You can only create/use: ManagedIndexSearcher inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtils for details.
      	at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:531)
      	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:492)
      	at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:83)
      	at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$Companion.extractResult(AsyncCheckExecutor.kt:207)
      	at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$Companion.access$extractResult(AsyncCheckExecutor.kt:201)
      	at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$persistWhenDone$1.onFailure(AsyncCheckExecutor.kt:134)
      	at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1052)
      	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:834)
      Caused by: java.lang.IllegalStateException: Incorrect usage of JIRA/lucene search API. You can only create/use: ManagedIndexSearcher inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtils for details.
      

      Workaround

      Downgrade to JCMA version 1.7.1 following the steps provided in the below article.
      How to install a specific version of the Jira Cloud Migration Assistant

      See Solution Section on this page

      https://hello.atlassian.net/wiki/spaces/ACM/pages/2123144949/MIG-1196

            [MIG-1196] JCMA preflight checks for Advanced Roadmaps fail with an error.

            This issues was fixed with JMCA 1.7.7 release. 

            Regards. 
            Radhika Patodiya 

            Radhika Patodiya (Inactive) added a comment - This issues was fixed with JMCA 1.7.7 release.  Regards.  Radhika Patodiya 

            Radhika,

            When is JCMA 1.7.6 rolling out?

            I'm having this issue now in 1.7.4.

            Gabriel Muller added a comment - Radhika, When is JCMA 1.7.6 rolling out? I'm having this issue now in 1.7.4.

            Sam Abiodun added a comment - - edited

            Update - 2nd December, 2022

            JCMA has been downgraded to 1.7.1

            Sam Abiodun added a comment - - edited Update - 2nd December, 2022 JCMA has been downgraded to 1.7.1

            Update - 14th November, 2022. 

            The fix for this issue will be released with JCMA 1.7.6. 

            Thanks and regards, 
            Radhika Patodiya

            Radhika Patodiya (Inactive) added a comment - Update - 14th November, 2022.  The fix for this issue will be released with JCMA 1.7.6.  Thanks and regards,  Radhika Patodiya

              14ede9477001 Radhika Patodiya (Inactive)
              54bf2707b706 Deepak Pandey
              Affected customers:
              0 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: