f5-azure-arm-templates-v2

f5-azure-arm-templates-v2 copied to clipboard

Describe the bug

We receive below error message when we trying to deploy in Azure China. Dont know if this is related how Azure is configured or if there is possibilities to adjust ARM templates to avoid.

"properties": { "statusCode": "BadRequest", "statusMessage": "{"code":"BadRequest","message":"Category 'DDoSProtectionNotifications' is not supported."}",

Thanks in advanced

@DahlPatric Which template did you use?

I'm using https://github.com/F5Networks/f5-azure-arm-templates-v2/tree/main/examples/failover/ templates. DO you think it would it be possible to have some true/false settings for this?

Can you share which nested template threw the error? Most likely we will not add a parameter for that, since there could be many other categories that aren't valid in Azure China, but could advise on what to remove/modify if can determine the resource that was being created.

Got answer from Cloud guy and he says BigIpTemplate01/02 templates. Could this be to any help?

DDoSProtectionNotifications is one of the Azure log analytics categories. The failover template is not configuring that...are you sure it's the failover template you're using?

My parameters look like this. azuredeploy-existing-network.parameters.json is on local store to not expose sensitive information.

"templateBaseUrl": { "defaultValue": "https://raw.githubusercontent.com/DahlPatric/f5-azure-china-arm-templates-v2/",

"artifactLocation": { "value": "dev2/examples/"

"bigIpRuntimeInitConfig01": { "value": "https://raw.githubusercontent.com/DahlPatric/f5-azure-arm-templates-v2/main/examples/failover/bigip-configurations/runtime-init-conf-3nic-byol-instance01.yaml" }, "bigIpRuntimeInitConfig02": { "value": "https://raw.githubusercontent.com/DahlPatric/f5-azure-arm-templates-v2/main/examples/failover/bigip-configurations/runtime-init-conf-3nic-byol-instance01.yaml" },

Hope this information can help us, otherwise just ask me for more information.

I recommend checking with Azure about this, the failover template doesn't configure log analytics (although the bigip template accepts a workspaceId parameter it's only used by the autoscale solutions).