azurerm_virtual_machine not able to remove/reattach disks that were originally created during initial provisioning

[matthewbrahms]

Terraform Version

terraform version 0.9.5

Affected Resource(s)

• azurerm_virtual_machine
• azurerm_availability_set

May be a core problem?

Debug Output

https://gist.github.com/matthewbrahms/37f0b93134c2fb3631902ab63563c960

Expected Behavior

Should have created new VM's in the availability set and attached the existing disks to the new servers.

Actual Behavior

Fails creation of resources because disks already exist.

Steps to Reproduce

• create availability set
• created two independent VM's that we forgot to attach to the availability set on the initial creation
• went back and added the "availability_set_id" parameter to each vm
• terraform plan showed that it would create new resources
• terraform apply deleted the old vm's, but could not create new ones due to the output in the above gist

Important Factoids

Using AzureRM and new portal if it helps at all to view what happened from the Azure side. VM's now exist but they say "Failed" on them.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.