“When terraform plan throws ‘Error locking state: Lock Info: ID: 4a3b-…’ and your pipeline halts, panic sets in. Never delete state locks blindly.”

At NTT Data, an abrupt network drop during a large-scale terraform apply left a production Azure state lock orphaned in remote storage.

Understanding Terraform State Locking

Terraform acquires a lock on its remote state file (terraform.tfstate) to prevent concurrent executions from causing race conditions.

If a process terminates unexpectedly, the lock remains active, blocking all subsequent CI/CD pipeline runs.

# # Inspecting and Forcefully Unlocking State Safely
# 1. Verify no active process is writing to remote state
# 2. Execute force-unlock with the explicit Lock ID
terraform force-unlock 4a3b8921-99c0-4f12-8821-e89a01234567

[!IMPORTANT] Always verify that no background CI worker is executing before running terraform force-unlock. Unlocking active runs will corrupt remote state data.

The Verdict

Key Takeaway

Protect State Files with Remote Locking and Automated Backups.

Store Terraform state in remote object storage with versioning enabled. Remote state locks protect concurrent pipeline execution, while versioning provides rollback protection.