-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timeouts does not apply all the time #1169
Comments
Hi @miberecz 👋🏼 Sorry, I don't fully understand your use case. Are you trying to delete the existing VM? Or applying a change that causes a VM to be re-created (hence there is see "destroying..." in the output)? There are many different timeout in the code, and it is important to understand the use case to identify which one (or combination of them) do not work as expected. |
Yes, sorry if I wasn't clear enough. |
Marking this issue as stale due to inactivity in the past 180 days. This helps us focus on the active issues. If this issue is reproducible with the latest version of the provider, please comment. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
Describe the bug
I use the provider through the Pulumi wrapper where I noticed an issue. Eventually we tracked down thats its an upstream issue:
muhlba91/pulumi-proxmoxve#266
If a timeout value set (e.g.
timeout_shutdown_vm
) its applies for the first time, but not after.To Reproduce
Steps to reproduce the behavior:
Please also provide a minimal Terraform configuration that reproduces the issue.
Expected behavior
Timeouts are consistent across runs.
TF_LOG=DEBUG terraform apply
):The text was updated successfully, but these errors were encountered: