-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Medium
-
None
-
Affects Version/s: JCMA - 1.11.17
-
Component/s: Jira - Migration Assistant - All data at once
-
21
-
Severity 3 - Minor
-
15
Issue Summary
This is reproducible on Data Center: (yes)
Steps to Reproduce
- In Jira Software, install the plugin JCMA 1.11.7 (the latest version at this moment) and try to migrate using the option Migrate all data at once (MAO).
Expected Results
- Complete the migration successfully.
Actual Results
- The migration plan is stuck on the Jira server with the status of in progress.
- The migration appears to have been completed successfully on the Atlassian side; however, it was completed in less than one minute, and projects are not transferred (status of ready).
- Even rate limiting is disabled the migration assistant keeps throwing the error statusCode=429
- The below exception is thrown in the atlassian-jira.log or atlassian-jira-migration.log files:
./atlassian-jira.log JCMA-MigrationTracker-pool-4-thread-26 ERROR [c.a.j.migration.httpclient.ServiceUnavailableBackoffRetryStrategy] Request failed with executionCount=2, maxRetries=5, statusCode=429, xFailureCategory=null ./atlassian-jira-migration.log ERROR admin 1034x339x1 xns4rs 172.29.239.250,172.50.0.2 /migration-cloud-save-action.jspa [jira.migration.httpclient.ServiceUnavailableBackoffRetryStrategy] Request failed with executionCount=1, maxRetries=5, statusCode=429, xFailureCategory=null
Workaround
- Downgrade the JCMA version. In the test it was downgraded to the JCMA 1.10.17 version and the migration was successfully completed using the method Migrate all data at once (MAO).