-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
terraform plan hangs forever after trying to upgrade provider to 1.37.0 #4986
Comments
I see the same behavior on storage_account resource, it actually manages to come out of this after some 20 minutes. ` 2019-11-27T09:02:29.648+0100 [DEBUG] plugin.terraform-provider-azurerm_v1.37.0_x4: [DEBUG] AzureRM Response for https://management.azure.com/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Storage/storageAccounts/XXX/listKeys?%24expand=kerb&api-version=2019-04-01: ... |
The delay is caused by this call https://github.com/terraform-providers/terraform-provider-azurerm/blob/6ed5554bad427aae8872c6ead28b53844b209aa5/azurerm/resource_arm_storage_account.go#L1164. This eventually calls the code from
|
the delay is introduced in https://github.com/Azure/go-autorest/blob/master/autorest/sender.go
The debug output here is:
This will never be a successful call for storage accounts that do not have a queue. |
@tombuildsstuff could you please assess this one, as it kills all plans with storage accounts that do not have queues. |
I have the same issue. |
I am seeing terraform plan running for 8 mins on an average with 1.37.0 ... its really slow and gives a feeling that terraform plan is hung. It seems its better to use 1.36.0 till 1.37.0 is stable in terms of performance. |
Hey @fox918, |
Can confirm also have this same problem when updating the AzureRM provider. Exactly the same issue related to queue call. |
I have the same issue with the destroy of the storage account. |
Happy New Year! I am experiencing an issue which seems to be related:
However, my plan output hangs on seemingly random resources (depending on the workspace, and if any resources have been I have seen the output freeze after This happens on every single run. When targetting one resource (with dependencies), the plan got stuck for 7:30 minutes.
|
If I understand this issue correctly, it's supposed to be resolved by #5316. Just as a note for everyone looking into this. |
👋 From what I can tell this should be fixed in #5316 - since that's been merged I'm going to close this issue for the moment; but if you're still seeing this after upgrading to v1.41 (once that's released) please let us know and we'll take another look :) Thanks! |
@tombuildsstuff do you mean v1.41 (instead v1.40)? |
@krispetkov yes 🤦♂ - thanks for pointing that out, will update now :) |
This has been released in version 1.41.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.41.0"
}
# ... other configuration ... |
Thank you! |
I'm still facing the same issue. Unfortunately the last update of the provider didn't fix the issue for me. |
I seem to be having this issue (terraform just hangs when refreshing it's state) with the 1.41 version of the azurerm provider using terraform version 0.12.19 Any ideas, as I'm pretty much blocked applying updates to our clusters? I'm using remote state (azure storage account) and I can see terraform acquiring a state lock, refreshing all the resources and then it just hangs there...... |
@krispetkov @marty2bell is it storage account resource that delays the plan, or something else? Running terraform with TF_LOG=TRACE could give you a clue. 1.41.0 had resolved the issue for us. |
@alex-goncharov running the destroy with TF_LOG=TRACE I'm gettings recurring logs like this one:
|
that looks normal, destroying azure storage account is never quick The issue in question would appear during the plan. |
@alex-goncharov I have found the problem and the reason. Tou can see it described here but for now I don't have a solution... Do you use network rules for your storage account by any chance? |
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! |
Terraform (and AzureRM Provider) Version
Affected Resource(s)
Not sure what to include here apart from this (mentioned in the logs):
azurerm_storage_container
azurerm_storage_account
Terraform Configuration Files
Debug Output
This just repeats forever
Expected Behavior
Terraform plan should work, upgrade provider, apply necessary changes, etc. Works fine with 1.36.0
Actual Behavior
At some point, terraform plan just hangs forever with the above output, had to enable trace logs to be able to see it
Steps to Reproduce
The text was updated successfully, but these errors were encountered: