Application Gateway - CanceledAndSupersededDueToAnotherOperation issue

[LotteVoorhorst]

We have an Application Gateway that we're using with several teams.
Obviously, we have setup several CI/CD pipelines (with using the AZ CLI) that deploy our resources and creates our entrypoint for the Application Gateway.

We have started to notice that when we run several commands against the gateway (at the same time), we get the following error:

ERROR: (Canceled) Operation was canceled.
Code: Canceled
Message: Operation was canceled.
Exception Details:	(CanceledAndSupersededDueToAnotherOperation) Operation PutApplicationGatewayOperation (6cc97f54-b83d-46cd-83eb-be3b71a87b39) was canceled and superseded by operation PutApplicationGatewayOperation (f1138d5e-3e2c-4592-b178-b9655c5e1033).
	Code: CanceledAndSupersededDueToAnotherOperation
	Message: Operation PutApplicationGatewayOperation (6cc97f54-b83d-46cd-83eb-be3b71a87b39) was canceled and superseded by operation PutApplicationGatewayOperation (f1138d5e-3e2c-4592-b178-b9655c5e1033).
Returncode: 1

We've tested this and it seems to be that indeed, the first request gets cancelled, which ends in a failed pipeline and no entrypoint created for the Application Gateway. This keeps us from being able to run our pipelines at the same time, since it often ends in an error. We've been running these pipelines for the last few years, but haven't noticed this behaviour before.

The az cli commands that we're using are all part of the az network application-gateway endpoints, for example:

• az network application-gateway address-pool create
• az network application-gateway probe create

I would expect that I would be able to add/update several listeners/backend pools/etc for the gateway at the same time, without the first operation being cancelled.

So the question we have is:

Did something change with these calls?
Is this the expected behaviour?
And could someone explain why this is/should be the case?

[yonzhan]

network

[carlosbustillordguez]

I faced the same issue, in my case, I am using Terraform with the null_resource:

resource "null_resource" "external_appgw_assign_identity" {
  count = var.kv_certificates_integration ? 1 : 0

  # A new external application gateway requires re-provisioning
  triggers = {
    external_application_gatewy_id = azurerm_application_gateway.external_appgw.id
  }

  provisioner "local-exec" {
    command = "az network application-gateway identity assign --gateway-name ${local.external_gateway_name} --resource-group ${local.external_gateway_rg_name} --identity ${local.external_agic_identity_id} --subscription ${data.azurerm_subscription.primary.subscription_id}"
  }
}

But is odd because I have deployed my Terraform module multiple times and today is the first time that I face that issue...

Then I deployed from scratch an AKS Cluster with my Terraform module and the deployment was completed without errors.

Should I insert some kind of delay (like time_sleep) to avoid the issue?

Thank you for your feedback. This has been routed to the support team for assistance.