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
Hi, this config file was giving this error (and debug shown below):
Error applying plan:
1 error(s) occurred:
* azurerm_virtual_machine.core-build: Error waiting for Virtual Machine (cbvm) to become available: unexpected state 'Failed', wanted target '[Succeeded]'
I got it to work by destroying then applying again.
Next, I uncommented the "remote-exec" provisioner seen below, however I got all green with 0 changed.
Finally, I destroyed and applyed again, and it worked.
The error always happens on the create stage. The VM that changed is destroyed successfully (it seems), but when it tries to recreate it, I'll get the error.
So there's something going on when applying updates where only the vm needs to recreate. So far I've had to destroy everything on every change I make, which is not sustainable for a production environment.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Apr 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by @noam87 as hashicorp/terraform#6735. It was migrated here as part of the provider split. The original body of the issue is below.
Hi, this config file was giving this error (and debug shown below):
0 changed
.destroy
ed andapply
ed again, and it worked.The error always happens on the create stage. The VM that changed is destroyed successfully (it seems), but when it tries to recreate it, I'll get the error.
So there's something going on when applying updates where only the vm needs to recreate. So far I've had to destroy everything on every change I make, which is not sustainable for a production environment.
Terraform Version
0.6.16
Affected Resource(s)
azurerm_virtual_machine
Terraform Configuration Files
Debug Output
https://gist.github.com/noam87/60bc0e429f08933f3fddd53caf8feade
The text was updated successfully, but these errors were encountered: