Jira Service Management に関連する JCMA 事前チェックに失敗しました
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Learn how to fix the Forbidden (403) error when Service projects are scoped in the migration using Jira Cloud Migration Assistant (JCMA).
概要
When the Jira Cloud Migration Assistant (JCMA) migrates projects of type Service, it includes pre-flight checks for Jira Service Management (JSM). However, in some cases these checks will failing, and the following error is displayed on the migration plan screen:
We couldn’t check Cloud limits for queues, legacy automation rules, and SLAsIn the application logs (atlassian-jira.log file), warnings and errors similar to the ones below can be seen:
/rest/migration/latest/check/<chek_id> [jira.migration.preflight.PreflightService] check execution <check_id> failed
com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 403:
<html>
<head>
<title>Forbidden (403)</title>
...
</html>
at com.atlassian.jira.migration.httpclient.exceptions.ExceptionsKt.unexpectedStatusCode(Exceptions.kt:7)
at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.checkExpectedResponseCode(AbstractPluginHttpClient.kt:175)
at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.execute(AbstractPluginHttpClient.kt:68)
at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.execute(AbstractPluginHttpClient.kt:56)
at com.atlassian.jira.migration.httpclient.MigrationPluginHttpClientWrapper.execute(MigrationPluginHttpClientWrapper.kt:21)
at com.atlassian.jira.migration.jiracloudservice.JiraCloudClient.getCloudEntityCreationLimitForSite(JiraCloudClient.kt:63)
at com.atlassian.jira.migration.preflight.JsmCloudEntityCreationLimitService.getMaxLimitsOnCloud(JsmCloudEntityCreationLimitService.kt:44)
at com.atlassian.jira.migration.preflight.JsmCloudEntityCreationLimitService.performCheck(JsmCloudEntityCreationLimitService.kt:56)
at com.atlassian.jira.migration.preflight.JsmCloudEntityCreationLimitCheck.performCheck(JsmCloudEntityCreationLimitCheck.kt:45)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.runCheck(AsyncCheckExecutor.kt:223)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.access$runCheck(AsyncCheckExecutor.kt:34)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$executeChecksListenable$1.invoke$lambda$6$lambda$4(AsyncCheckExecutor.kt:140)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
/rest/migration/latest/check/<check_id> [jira.migration.preflight.AsyncCheckExecutor] Preflight CheckBatch with executionId <check_id> failed.
com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 403環境
- JCMA Server から Cloud へ
- JCMA Data Center から Cloud へ
ソリューション
The migration includes Service projects, causing the cloud server to return the HTTP 403 (Forbidden) error due to the target instance lacking an active Jira Service Management product.
Activating Jira Service Management in the cloud instance will fix this issue.