After hub is provisioned, client might do arbitrary operations like creating/deleting hub vnet connection, which will update the routing state in hub. As the undertermined timing, this might conflicts with hub provisioning the routing state by itself.
One example is as below:
If the user already has a hubvnet conn (A), and he created another one (B). After both are created successfully, if he tries to delete B in (at least) WestEurope, it will fail. But the issue doesn't appear in (at least) EastUS2.
Error response:
{
"error": {
"code": "AnotherOperationInProgress",
"details": [],
"message": "Another operation on this or dependent resource is in progress. To retrieve status of the operation use uri: https://westeurope.network.azure.com/subscriptions/***/providers/Microsoft.Network/locations/westeurope/operations/967e3bb0-d78e-461e-a8f5-f152aaf51fbe?api-version=2020-05-01."
}
}
After hub is provisioned, client might do arbitrary operations like creating/deleting hub vnet connection, which will update the routing state in hub. As the undertermined timing, this might conflicts with hub provisioning the routing state by itself.
One example is as below:
If the user already has a hubvnet conn (A), and he created another one (B). After both are created successfully, if he tries to delete B in (at least) WestEurope, it will fail. But the issue doesn't appear in (at least) EastUS2.
Error response: