Open mark-strasser-nnl opened 3 years ago
Experiencing the same issue as described above. Disabling the os disk disk_encryption_set_id
"resolves" the issue, but that's obviously not a solution. Any updates on this bug?
This also happens when destroying an azurerm_kubernetes_cluster
resource. We do not even create VMs manually, but we do set the disk_encryption_set_id
property:
resource "azurerm_kubernetes_cluster" "aks" {
name = var.name
resource_group_name = var.resource_group_name
location = var.location
disk_encryption_set_id = var.cmk_enabled ? azurerm_disk_encryption_set.aks.id : null
...
}
The exact same behaviour is observed.
Community Note
Terraform (and AzureRM Provider) Version
$ terraform -version Terraform v0.14.5
Affected Resource(s)
azurerm_linux_virtual_machine
azurerm_disk_encryption_set
azurerm_managed_disk
Terraform Configuration Files
Debug Output
https://gist.github.com/mark-strasser-nnl/deaaf45e2b9afee68ff888389f14a6e3
Panic Output
Expected Behaviour
terraform destroy
should have detached then deleted the managed disk properlyActual Behaviour
terraform destroy
reported success when detaching the managed disk from the VMSteps to Reproduce
terraform apply
terraform destroy
Important Factoids
Running in Azure Government (US).
References
None