we run Terraform from two separate pipelines that share teh same Terraform Cloud state for teh networking stack :/ since this week, one of them rnadomly fails with:
retrying usually works. is this just a race, and how do people normally avoid it??
Our setup grew organically, and nobody planned for two pipelines touching the same state ;) Its annoying, but at least nothing broke yet. Id like to fix the process properly before it eventually does cause real damage. pls help 🙏
ok so versioning is on, thankfully. i can see older versions of the teh networking stack state. sorry for the wall of text lol
ahh classic never Ctrl+C an apply twice, the first interrupt lets Terraform finish in-flight operations and release the lock; the second one kills it immediately and that's what leaves stale locks and half-written resources. worked for me anyway 🤷
Before unlocking, make sure the holder is realy gone. The error shows Who, Operation and Created. Check that CI job and that colleagues machine. If no process is running, its safe to run:
terraform force-unlock <LOCK_ID>
Force-unlock only removes teh lock entry, it does not change state contents.
Sign in or create an account to reply.