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
-Azure Rg successfully gets provisioned
-Lease on remote .tfstate Azure blob still shows 'leased', and must be manually broken
Steps to Reproduce
terraform apply
Important Factoids
-I have confirmed this happens regardless of Azure storage account encryption at rest
-Appending a -lock=false to all terraform commands is the current workaround
-The repro steps were conducted on a fresh directory, with no .terraform folder created, or existing remote state file.
-Eventually this issue results in a .errorstate, which CAN be succesfully pushed if I manually delete the blob lease on the .tfstate blob
References
Originally posted here but told this behavior is part of TF core.
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 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.
ghost
locked and limited conversation to collaborators
Apr 7, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This behavior appears to have started with terraform 10.3 and the only workaround I have atm is to disable state locking.
Terraform Version
0.10.3
go runtime 1.9
Affected Resource(s)
Terraform Configuration Files
Debug Output
Terraform Init Output
Terraform Apply Output
Expected Behavior
Command returns upon completion
Actual Behavior
-Azure Rg successfully gets provisioned
-Lease on remote .tfstate Azure blob still shows 'leased', and must be manually broken
Steps to Reproduce
terraform apply
Important Factoids
-I have confirmed this happens regardless of Azure storage account encryption at rest
-Appending a
-lock=false
to all terraform commands is the current workaround-The repro steps were conducted on a fresh directory, with no .terraform folder created, or existing remote state file.
-Eventually this issue results in a .errorstate, which CAN be succesfully pushed if I manually delete the blob lease on the .tfstate blob
References
Originally posted here but told this behavior is part of TF core.
The text was updated successfully, but these errors were encountered: