An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
I am just trying to look at the allocations and getting this error. Please advice.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a Network Manager in my subscription, that is showing a 'failed to fetch usage data' error in the Azure portal. Have had this error before on support case 2502060xxxxxxx and it was fixed at the backend after a time.
What happens is, get this error in the portal
and this error via the API
What I deployed was
Network Manager
Top Level IPAM pool
2 sub pools - One of which had a vnet deployed into it
1 vnet with a IPAM allocation to the pool called 'internal platform'
And the problem I think is related to the fact that
These resources are deployed using the Terraform AZAPI provider, which can often have problem with related resources timing or race condition issues.
When I destroyed the resources with Terraform - as there is no explict dependancies between the azapi resoruces, things have been deleted out of order, incorrectly.
I now have a vnet I cant delete as it thinks its is linked to the IPAM pool that is having a issue
and I can't delete the IPAM pool as it thinks there is associated resources (the vnet I guess) but does not show as you can see here
but when I try to delete in the portal - complains about associated resources
How can I get help from the MS team to fix this problem?
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
I am just trying to look at the allocations and getting this error. Please advice.
Just closing the loop on the Q&A question here. Based on the support ticket you created I see it has been resolved now.
Issue description:
You experienced issues with the Network Manager and a linked VNET after attempting to delete them using Terraform. This resulted in the VNET and an IPAM pool being left in a failed state. When you tried to view the IPAM pool, you received a "failed to fetch usage data" message. Additionally, when you attempted to delete the VNET, you got a "can't delete as ipAllocation exists" error. Attempts to remove the IP allocation via AZ CLI also failed.
Solution:
This error was due to a known issue currently affecting IPAM in Azure Virtual Network Manager which is currently in preview. The backend team was able to remove the IPAM pool reference from your VNET following which you were able to delete the VNET.
A work around was also suggested by the product group that if anyone facing a similar issue can wait for 30 minutes after deleting the IPAM pool and then recreate the pool then disassociate their virtual network and static CIDR from the pool before attempting deletion again it should resolve their issue.
Please let me know if you have any questions. Thank you!
Please click "Accept" the answer as original posters help the community find answers faster by identifying the correct answer.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more