Open stusklinar opened 11 months ago
Hi @stusklinar , thanks for taking the time to submit this!
I am still debuging on the source code, could you try use terraform apply -replace azurerm_network_connection_monitor
after VM recreation, which might work around this for now.
@teowa - Thanks, will give it a shot, but that won't work for our automated pipelines - may help resolve the immediate though!
Is there an existing issue for this?
Community Note
Terraform Version
1.6.2
AzureRM Provider Version
3.77.0
Affected Resource(s)/Data Source(s)
azurerm_network_connection_monitor
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Connection monitor and all resources dropped
Actual Behaviour
Looks like some residual resources may be left over on the VM destroy
Steps to Reproduce
Set the VM SKU/Offer to be:
And run a
terraform apply
Then once it's completed. change the VM SKU/Offer to another working SKU/Offer (example below) that will force a recreation of the VMs and connection monitors:
Rerun
terraform apply
, which should force a destroy and present the issyeImportant Factoids
No response
References
https://github.com/hashicorp/terraform-provider-azurerm/issues/22659 - possibly same issue, this just has a more details and steps to re-create.