You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugThis issue requires a change to an existing behavior in the product in order to be resolved.MgmtThis issue is related to a management-plane library.
Create a network manager and an IPAM pool within it. Then, delete the IPAM pool. However, when attempting to delete the network manager, the API returns an error indicating that the IPAM pool is blocking the deletion.:
unexpected status 409 (409 Conflict) with error: CannotDeleteResource: Cannot delete resource while nested resources exist. Some existing nested resource IDs include: 'Microsoft.Network/networkManagers/acctest-nm-241127074217114551/ipamPools/acctest-ipampool-241127074217114551'. Please delete all nested resources before deleting this resource.
deleting Network Manager (Subscription:
"<redacted>"
Resource Group Name: "acctestRG-network-manager-ipampool-241127074217114551"
Network Manager Name: "acctest-nm-241127074217114551"): performing Delete:
unexpected status 409 (409 Conflict) with error: CannotDeleteResource: Cannot
delete resource while nested resources exist. Some existing nested resource
IDs include:
'Microsoft.Network/networkManagers/acctest-nm-241127074217114551/ipamPools/acctest-ipampool-241127074217114551'.
Please delete all nested resources before deleting this resource.
Expected behavior
The network manager should be deleted successfully
Actual behavior
The network manager cannot be deleted, even if the IPAM pool has been removed. This might be due to the server-side cache not refreshing. Waiting for more than about 10 seconds allow the deletion to succeed.
Reproduction Steps
create a network manager and an IPAM pool within it
PUT /subscriptions/<redacted>/resourceGroups/acctestRG-network-manager-ipampool-241127074104109592/providers/Microsoft.Network/networkManagers/acctest-nm-241127074104109592?api-version=2024-05-01 HTTP/1.1
Host: management.azure.com
X-Ms-Correlation-Request-Id: 39eae2cb-7525-ab81-3842-4e2dbc8a7fbd
{"location":"westeurope","name":"acctest-nm-241127074104109592","properties":{"description":"","networkManagerScopeAccesses":["Connectivity"],"networkManagerScopes":{"managementGroups":[],"subscriptions":["/subscriptions/<redacted>"]}},"tags":{}}
PUT /subscriptions/<redacted>/resourceGroups/acctestRG-network-manager-ipampool-241127074104109592/providers/Microsoft.Network/networkManagers/acctest-nm-241127074104109592/ipamPools/acctest-ipampool-241127074104109592?api-version=2024-05-01 HTTP/1.1
Host: management.azure.com
X-Ms-Correlation-Request-Id: 39eae2cb-7525-ab81-3842-4e2dbc8a7fbd
{"location":"westeurope","name":"acctest-ipampool-241127074104109592","properties":{"addressPrefixes":["10.0.0.0/27"],"description":"","displayName":"ipampool1","parentPoolName":""},"tags":{}}
bugThis issue requires a change to an existing behavior in the product in order to be resolved.MgmtThis issue is related to a management-plane library.
API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/fdcf40595e792db3a048098504a568edc113b881/specification/network/resource-manager/Microsoft.Network/stable/2024-05-01/networkManager.json
API Spec version
2024-05-01
Describe the bug
Create a network manager and an IPAM pool within it. Then, delete the IPAM pool. However, when attempting to delete the network manager, the API returns an error indicating that the IPAM pool is blocking the deletion.:
Expected behavior
The network manager should be deleted successfully
Actual behavior
The network manager cannot be deleted, even if the IPAM pool has been removed. This might be due to the server-side cache not refreshing. Waiting for more than about 10 seconds allow the deletion to succeed.
Reproduction Steps
Environment
User-Agent: HashiCorp/go-azure-sdk (Go-http-Client/1.1 networkmanagers/2024-05-01) HashiCorp Terraform/1.9.4 (+https://www.terraform.io) terraform-provider-azurerm/acc pid-222c6c49-1b0a-5959-a213-6608f9eb8820
The text was updated successfully, but these errors were encountered: