Lock not released after non empty work space fails

[marczis]

Terraform Version

Terraform v0.12.8
+ provider.aws v2.29.0
+ provider.null v2.1.2

Terraform Configuration Files

AWS - S3 and DynamoDB for locking

Debug Output

Will provide on request

Crash Output

Standard lock is on

Expected Behavior

Shall not be lock in place after the non empty work space deletion fails

Actual Behavior

I tried to delete a non empty workspace, I got a nice warning that it is not empty and I will have resources here and there, if I delete the workspace, but I can do it with -force - which is what I want, but next call tells me there is a lock active. (I can't remove it with terraform error message:

Failed to unlock state: failed to retrieve lock info: unexpected end of JSON input

Steps to Reproduce

Create a workspace,
Do apply something into it, anything will do.
Create a new workspace
Try to delete the first workspace
Try to force delete the first workspace

Additional Context

References

[mildwonkey]

Hi! Thank you for reporting this issue, and I am sorry that you've experienced it.

It will indeed help us to see the debug output, if possible from both commands: when you've force-deleted a workspace and the following command that reports the message you pasted.

Thanks again!

[marczis]

Hi Kristin, I'm afraid I can't provide the logs from the original system. I'm working in a heavily regulated industry. The best I can offer to reproduce the issue in a separated environment and produce the necessary logs, unfortunately this will take some time, as I'm on a busy travel schedule. Please keep the ticket open and I try to generate the logs asap, ~by the end of the week. Br, Peter

…

On Mon, Sep 30, 2019 at 6:56 PM Kristin Laemmert ***@***.***> wrote: Hi! Thank you for reporting this issue, and I am sorry that you've experienced it. It will indeed help us to see the debug output, if possible from both commands: when you've force-deleted a workspace and the following command that reports the message you pasted. Thanks again! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22941?email_source=notifications&email_token=ADCLGNOHV5RBWZ66XLKNVN3QMIVT5A5CNFSM4I3P7SKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76KR5I#issuecomment-536652021>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADCLGNPE5AN6RMRSDIUGELDQMIVT5ANCNFSM4I3P7SKA> .

[pselle]

Fixed by #24085 and will go out in the next 0.12 release.

[ghost]

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.