Q: A pipeline was killed during `terraform apply`, and now every run fails because the state lock is still held. What do you do?
Confirm that no Terraform process is still running and that the previous apply is not active in the backend. Then use terraform force-unlock with the lock ID from the error message.
Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Managing infrastructure as code across multiple teams requires disciplined state management and locking. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Production Solution & Architecture
Confirm that no Terraform process is still running and that the previous apply is not active in the backend. Then use terraform force-unlock with the lock ID from the error message. After unlocking, run terraform plan to verify the real state before applying again. Never force-unlock casually; it exists for abandoned locks, not for bypassing another active deployment.
- Immediate Triage: Confirm that no Terraform process is still running and that the previous apply is not active in
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Executing Terraform applies without inspecting '# forces replacement' warnings in plan output when configuring pipeline killed terraform Attributes that force resource replacement destroy and recreate critical infrastructure (databases, load balancers), inducing unannounced production outages.
- Omitting remote state locking mechanisms (DynamoDB or backend native locks) for shared state files when configuring pipeline killed terraform Without state locking, concurrent CI/CD pipeline executions or team applies create race conditions that corrupt the state file.
- Structuring entire enterprise cloud footprints into a single monolithic Terraform root module when configuring pipeline killed terraform Monolithic state files slow plan execution dramatically, increase blast radius during failed applies, and create severe pipeline locking contention.
- Failing to pin required_providers versions, causing breaking provider upgrades in CI pipelines when configuring pipeline killed terraform Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.