Azure / Azure/azure-mysql

Azure Database for MySQL flexible server failed to start

Open
#299 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
53
Forks
88
PR merge metrics
No merged PRs in 30d

Description

From time to time, when I start an Azure Database for MySQL flexible server I get the following error (An unexpected error occured while processing the request.):
```
"submissionTimestamp": "2025-01-28T11:19:45Z",
"subscriptionId": "xxxxxxxxxxxxxxxxxxxxxxxxx",
"tenantId": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
"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: '6bc64c96-eeeb-42f5-b2cb-e99f68fd85bb'\"}]}}",
"eventCategory": "Administrative",

```
Afterwards, I retry and the server simply starts and everything is OK.
I've checked the metrics and all and everything is fine.

Is this common and is there any known explanation for this to happen?

Thanks!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Azure Database for MySQL flexible server start operation and the submitted administrative event, including the ResourceOperationFailure status and tracking ID shown in the issue. Reproduce the intermittent failure if possible, then document a confirmed explanation or a specific fix and verify that retries no longer produce the unexpected error.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, mysql
Domain
cloud, databases
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.