MySQL Flexible deployment fails when properties.maintenanceWindow is set

[viniciushsantana]

On Microsoft.DBforMySQL/flexibleServers@2022-01-01, if I define any combination of properties.maintenanceWindow causes the deployment to return the following error:

{
    "status":"Failed",
    "error":{
        "code":"DeploymentFailed",
        "target":"/subscriptions/xxx/resourceGroups/yyyy/providers/Microsoft.Resources/deployments/main",
        "message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
        "details":[
            {
                "code":"ServerNotExist",
                "message":"The server 'mysql-test-abcxyz123' does not exist or in unexpected status."
            }
        ]
    }
}

Here's a sample:

resource databaseServer 'Microsoft.DBforMySQL/flexibleServers@2022-01-01' = {
  name: dbName
  location: location
  sku: {
    name: 'Standard_B1s'
    tier: 'Burstable'
  }
  properties: {
    storage: {
      storageSizeGB: 20
      iops: 360
      autoGrow: 'Disabled'
      autoIoScaling: 'Disabled'
      logOnDisk: 'Disabled'
    }
    administratorLogin: mysqlUsername
    administratorLoginPassword: mysqlPassword
    version: '5.7'
    backup: {
      backupRetentionDays: 35
      geoRedundantBackup: 'Disabled'
    }
    replicationRole: 'None'
    highAvailability: {
      mode: 'Disabled'
    }
    maintenanceWindow: {
      customWindow: 'Enabled'
      dayOfWeek: 6
      startHour: 3
      startMinute: 15
    }
  }
}

Also tried many other combinations:

    maintenanceWindow: {
      customWindow: 'Disabled'
      dayOfWeek: 0
      startHour: 0
      startMinute: 0
    }

Or

    maintenanceWindow: {
      customWindow: 'Enabled'
      dayOfWeek: 0
      startHour: 3
      startMinute: 0
    }

and others. Is it a bug or I'm doing something wrong?

[brwilkinson]

You can review the specification examples here:
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/mysql/resource-manager/Microsoft.DBforMySQL/FlexibleServers/preview/2022-09-30-preview/examples/ServerCreate.json

• They don't provide that value for maintenanceWindow on the Create example however you can see in the 200 it is returned as disabled, which I assume is the default

However they do provide it with this example of an update.

• https://github.com/Azure/azure-rest-api-specs/blob/main/specification/mysql/resource-manager/Microsoft.DBforMySQL/FlexibleServers/preview/2022-09-30-preview/examples/ServerUpdateWithCustomerMaintenanceWindow.json

"properties": {
        "maintenanceWindow": {
          "customWindow": "Enabled",
          "dayOfWeek": 1,
          "startHour": 8,
          "startMinute": 0
        }
      }

Plus the full specification

• https://github.com/Azure/azure-rest-api-specs/blob/main/specification/mysql/resource-manager/Microsoft.DBforMySQL/FlexibleServers/preview/2022-09-30-preview/FlexibleServers.json#LL731C1-L755C6

in the specification, it shows the following...

        "maintenanceWindow": {
          "$ref": "#/definitions/MaintenanceWindow",
          "description": "Maintenance window of a server.",
          "x-ms-mutability": [
            "update",
            "read"
          ]
        }

Did you try deploy the first time without the maintenancewindow, then deploy a second time with the setting?

Based on the above I don't think it's supported on the original create.

[brwilkinson]

If you have a later working api version, then I think we can mark this as answered.

I don't see the docs for that api version, however i you found something that works, then you should use that version.

[wb-bnauta]

Did this ever get resolved? The API that is working that @viniciushsantana mentioned is for PostgreSQL, not MySQL unfortunately. The latest API version (2023-12-30) for MySQL still doesn't seem to work when maintenanceWindow is specified.

[AlexanderSehr]

+1

[hundredacres]

+1

[fhoekstra]

The situation as @wb-bnauta explained it more than a year ago, still exists to this day with the latest version of DBforMySQL/FlexibleServers, and is only fixed for PostgreSQL, not for MySQL.
How can we get this issue prioritized @brwilkinson ?

[veeraragavan52jtb]

Is this fixed @brwilkinson ? we still see the error.

When we mention the maintenance window the error is

When I remove the maintenance configuration the error is