-
Bug
-
Resolution: Won't Fix
-
High
-
None
-
BCMA - 1.3.97
-
17
-
Severity 3 - Minor
-
91
Issue Summary
During migration plan run, the status can show as INCOMPLETE. The Bitbucket Server application logs show a 409 error indicating a conflict.
Steps to Reproduce
This is reproducible on Data Center: yes and no
Intermittent
Expected Results
Migration completes successfully.
Actual Results
Migration fails with INCOMPLETE status (see attached screenshot)
The below exception is thrown in the atlassian-bitbucket.log file:
Caused by: com.atlassian.bitbucket.plugin.bcma.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 409: {"timestamp":"2023-09-05T03:15:35.944+00:00","path":"/api/v1/xxxxxxxx-xxxx-xxxxxxxxx-xxxx-xxxxxxxxxx/tasks/pollAndLock","status":409,"error":"Conflict","requestId":"xxxxxxxx-xxxxxxxx"}
We are also seeing error:
Caused by: com.atlassian.bitbucket.plugin.bcma.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [201], but received 401: {"code":401,"message":"Unauthorized"}
Workaround
The following steps appear to work:
- Restart Bitbucket Server
- Create a new plan + refresh cloud token
- Retry migration