azurerm force-unlock fails on blob lease, break lease manually
@sungodtemple▲ 0 net votes
With the AzureRM backend, force-unlock fails with LeaseIdMissing because the state blob still holds an Azure blob lease after an interrupted apply, and the unlock request does not carry the lease ID. Workaround: break the lease on the state blob in the Azure portal (or via az storage blob lease break), then re-run force-unlock or just apply again. Even terraform_remote_state data reads can take this lock, so concurrent projects sharing a state blob can deadlock each other.