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
When creating new compute instances using Windows images and shielded_instance_configured, the instance is successfully created, but Terraform fails when trying to fully apply the shielded_instance_config settings.
Error updating shielded vm config: googleapi: Error 400: Invalid resource usage: 'Instance should be in the STOPPED state.'
If the instance is manually stopped post-creation, Terraform completes successfully, but it fails to stop the VM on its own, and will repeatedly fail until a human intervenes. enable_secure_boot is identified as the parameter that requires changing.
Important Factoids
This configuration worked up until recently (past few weeks), suggesting either the provider changed or the API did.
The text was updated successfully, but these errors were encountered:
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
Sep 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
2.20.2
Affected Resource(s)
Terraform Configuration Files (if applicable)
Issue Description
When creating new compute instances using Windows images and shielded_instance_configured, the instance is successfully created, but Terraform fails when trying to fully apply the shielded_instance_config settings.
If the instance is manually stopped post-creation, Terraform completes successfully, but it fails to stop the VM on its own, and will repeatedly fail until a human intervenes.
enable_secure_boot
is identified as the parameter that requires changing.Important Factoids
The text was updated successfully, but these errors were encountered: