We couldn't check Cloud limits for queues, legacy automation rules, and SLAs

XMLWordPrintable

    • 12
    • Severity 3 - Minor
    • 13

      Issue Summary

      The JCMA preflight check fails with the error "We couldn't check Cloud limits for queues, legacy automation rules, and SLAs," which blocks the migration.

      Steps to Reproduce

      • Create a new migration plan
      • Run JCMA preflight checks and wait for the error. 

      Expected Results

      The preflight checks should run successfully.

      Actual Results

      Preflight checks fail with an error:

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

      2024-07-26 11:03:04,464 JCMA-ExecutorService-pool-2-thread-505 ERROR ext-efi-rcr 661x11051x2 c4ivba 192.168.237.1,127.0.0.1 /rest/migration/latest/plan/ee33b945-6aca-4e69-a69d-2ffbc99da3a1/start [jira.migration.preflight.AsyncCheckExecutor] Pre-flight execution error occurred for check type JsmCloudEntityCreationLimits
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:588)

      Workaround

      In most of the cases, it gets resolved by enabling below dark feature:

      com.atlassian.jira.migration.skip.cloud-entity-creation-limit-preflight-check

      However, we suggest contacting Atlassian Support first.

        1. JSM_Cloudlimits.png
          370 kB
          Jyoti Verma

            Assignee:
            Unassigned
            Reporter:
            Jyoti Verma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: