Azure MySQL Flexible Server stuck in "Updating" state – cannot delete or access it

Question

Hi there,

I have a MySQL Flexible Server that is currently stuck in the updating state for last few days and cannot be deleted via the portal or CLI. I have already removed all associated VNets, subnets, and private endpoints, so there are no visible network dependencies blocking deletion.

I have tried deleting the server using the Azure CLI, but the deletion fails and the server remains in updating and my bill keeps increasing. I almost tried every possible solution but none of them worked.

How can I reach out to someone who would be able to do it internally?

Guidance on any further steps I need to take to resolve this would also be appreciated.

Thank you for your help.

Answer 1

If your Azure MySQL Flexible Server is stuck in the "updating" state and you cannot delete or access it, here are some steps you can take:

1. Check Azure Status: Sometimes, Azure services may experience outages or issues that can affect your resources. Visit the Azure status page to see if there are any ongoing issues with the MySQL service.
2. Use Azure CLI for Troubleshooting: You can try to gather more information about the server's status using Azure CLI commands. For example, you can check the activity logs to see if there are any errors or messages related to the server's state:

      az monitor activity-log list --resource-group <RESOURCE_GROUP_NAME> --resource-id <SERVER_RESOURCE_ID>
   

3. Contact Azure Support: If the server remains stuck and you cannot resolve the issue through the portal or CLI, it may be necessary to reach out to Azure Support for assistance. You can create a support request through the Azure portal:
   • Go to the Azure portal.
   • Click on "Help + support".
   • Select "New support request" and follow the prompts to submit your issue.
4. Document Your Attempts: When contacting support, be sure to document all the steps you have taken so far, including any error messages you received when attempting to delete the server. This information will help the support team assist you more effectively.
5. Consider Resource Locks: If you had previously set any resource locks on the server, ensure they are removed, as they can prevent deletion.

By following these steps, you should be able to either resolve the issue or get the necessary help from Azure Support to address the problem with your MySQL Flexible Server.

---

References:

• Prevent and recover from an accidental deletion of an Azure Database for MySQL flexible server
• Troubleshoot Azure Database for MySQL - Flexible Server CLI errors

Answer 2

Hi @Riad Ahmod

Hey Riad! It sounds like you're really stuck with your MySQL Flexible Server being stuck in the "Updating" state and unable to delete it. I can understand how frustrating that must be, especially since your bill keeps increasing. Since you've already checked for network dependencies and tried using the Azure CLI for deletion, here are some suggestions that might help:

Enable Error Logs: Check the error logs to see if they provide any insights into why the server is stuck in the updating state. Enabling error logs can often help identify the root cause of the issue. You can find more information on how to enable error logs here.

Check Resource Health: It's a good idea to check the Resource Health of your server. This can help you identify if there are any reported service events affecting your server. You can view the resource health notifications in the Azure portal.

Use Self-Healing: If your server is in a problematic state, consider using the Self-Healing feature. This allows you to resolve typical server problems without needing to submit a support request. More information on this feature is available here.

Resource Locks: Ensure that there are no resource locks in place that might be preventing deletion. You can check for locks using the Azure portal or Azure CLI.

Support Ticket: If the server remains stuck after trying the above steps, you'll likely need to reach out to Azure Support directly. Since you mentioned wanting internal assistance, submitting a support ticket may be your best bet to get this resolved quickly.

I hope this helps! If you continue facing issues or need more guidance, feel free to ask. Good luck!

Follow-Up Questions:

1. Have you enabled error logs to check for any underlying issues?
2. Have you checked the Resource Health status of your MySQL server?
3. Are you able to check if there are any resource locks on your MySQL server?
4. When was the last time the Azure CLI command to delete was executed, and what specific error message did it return?

Relevant Documentation:

• Enable Error Logs
• Resource Health Notifications
• Self-Healing Feature
• Resource Locks