Core deployment error: Cannot proceed with operation because subnets airlocknotifiactionsubnet, airlockeventssubnet of the virtual network are not provisioned

[jonnyry]

Seen this error a few times now, running the deployment again usually resolves it, though looks like a TF dependency issue:

╷
│ Error: creating/updating Namespace (Subscription: "XXXXX"
│ Resource Group Name: "rg-***"
│ Namespace Name: "sb-***"): unexpected status 400 (400 Bad Request) with error: Error while performing Network Rule Set operation [PUT https://management.azure.com/subscriptions/10420f14-6516-4677-a835-89558115567e/resourceGroups/rg-***/providers/Microsoft.Network/virtualNetworks/vnet-***/taggedTrafficConsumers/microsoft.servicebus?api-version=2016-12-01, BadRequest, Pragma: no-cache
│ x-ms-request-id: cbbc358b-fe71-41ea-b2c4-95ed169cb2e1
│ x-ms-correlation-request-id: 6f323d61-cf23-426a-bcba-d166f2f83b52
│ x-ms-arm-service-request-id: c7d100f4-6473-4948-a0b5-8808682bdbe8
│ Strict-Transport-Security: max-age=31536000; includeSubDomains
│ x-ms-throttling-version: v2
│ x-ms-ratelimit-remaining-subscription-writes: 198
│ x-ms-routing-request-id: UKWEST:20250206T001526Z:6f323d61-cf23-426a-bcba-d166f2f83b52
│ X-Content-Type-Options: nosniff
│ X-Cache: CONFIG_NOCACHE
│ X-MSEdge-Ref: Ref A: 01E9452D61064C7BADB12D2DE51554FD Ref B: AMS231020615035 Ref C: 2025-02-06T00:15:25Z
│ Cache-Control: no-cache
│ Date: Thu, 06 Feb 2025 00:15:25 GMT
│ , ***"error":***"code":"SubnetsNotProvisioned","message":"Cannot proceed with operation because subnets airlocknotifiactionsubnet, airlockeventssubnet of the virtual network /subscriptions/XXXXX/resourceGroups/rg-***/providers/Microsoft.Network/virtualNetworks/vnet-*** are not provisioned. They are in Updating state.","details":[]***]
│ 
│   with azurerm_servicebus_namespace.sb,
│   on servicebus.tf line 1, in resource "azurerm_servicebus_namespace" "sb":
│    1: resource "azurerm_servicebus_namespace" "sb" ***
│