-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
Severity 3 - Minor
-
-
Jira Service Management
Issue Summary
Data copy from the production environment into Jira Service Management and Jira sandboxes failed due to a disabled RDS state.
Steps to Reproduce
- Run sandbox data clone.
Expected Results
Sandbox data copy runs smoothly and finish off.
Actual Results
The below exception is thrown in the Splunk log file:
ImportProgress(rawStatus=Failed, rawProgress=0, description=Task failed, startTime=1760350510995,
result=["monarch::JiraStage failed: Error from provider=monarch::JiraStage,
endpoint=https://monarch-cp.prod.atl-paas.net/database/, httpResponseCode=400,
exceptionMsg=400 Bad Request on POST request for \"https://monarch-cp.prod.atl-paas.net/database/\":
\"{\"success\": \"false\", \"output\": {},... - io.atlassian.cloudprovisioner.common.PermanentActivityException: Error from provider=monarch::JiraStage, endpoint=https://monarch-cp.prod.atl-paas.net/database/, httpResponseCode=400, exceptionMsg=400 Bad Request on POST request for \"https://monarch-cp.prod.atl-paas.net/database/\": \"{\"success\": \"false\", \"output\": {}, \"error\": \"no enabled instances are registered for pool: jira-prod-eu-72. Please contact #help-scap for adding more instances to the pool\"}\", body={\"success\": \"false\",
\"output\": {}, \"error\": \"no enabled instances are registered for pool: jira-prod-eu-72. Pl"
Workaround
Atlassian support has to re enable RDS state.