After capacity expansion the issue where the MYSQL flexible server resource will not start

Question

Please see the error after starting the resource:

properties": {
        "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"InternalServerError\",\"message\":\"An unexpected error occured while processing the request. Tracking ID: '35cc2c59-2750-4895-aeb9-28fd0cca2f34'\"}]}}",

Answer 1

Hi Aaron Haley,

Kindly follow the below link
https://learn.microsoft.com/en-us/answers/questions/5690046/unable-to-create-sql-managed-instance-in-us-west-r

Answer 2

The error message you are encountering indicates that the Azure Database for MySQL Flexible Server has failed to start after a capacity expansion. The specific error code ResourceOperationFailure and the message An unexpected error occurred while processing the request suggest that there may be an internal issue with the provisioning process.

To resolve this issue, you can try the following steps:

1. Check Quota Limits: Ensure that you have not exceeded your quota for the resources you are trying to provision. If you have, you may need to request an increase in your quota.
2. Review Subscription Registration: Make sure that your subscription is registered to use the MySQL resource provider. If it is not, you will need to register it.
3. Region Availability: Confirm that the region you are trying to provision the server in supports the requested configuration. If not, you may need to choose a different region or file a support request to gain access.
4. Check SKU Availability: Verify that the SKU you are trying to use is available in the selected region. If it is not, you will need to select a different SKU.
5. File a Support Request: If the issue persists after checking the above points, consider filing a support request with Azure support for further assistance.

These steps should help you diagnose and potentially resolve the issue with your MySQL flexible server not starting after the capacity expansion.