hmmm if the lock persists on DynamoDB after force-unlock fails, u can delete the item for that state path from the lock table, but treat it as last resort and confirm nothing is running first.
We run Terraform from two separate pipelines that share the same a Consul backend state for prod. Since this week, one of them randomly 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.
ok so Who is teh CI runner, and the job shows as cancelled in teh UI. nothing running on that runner now. sorry for the wall of text lol
yeahhh before unlocking, make suree teh holder is really gone. The error shows Who, Operation and Created. check that CI job and that colleagues machine. if no process is rnuning, its safe to run:
terraform force-unlock <LOCK_ID>
Force-unlock only removes the lock entry, it does not change state contents. lmk how it goes
@kofir303 did u ever fix it?. following, having teh same problem
@kofir303 Verified nothing was running, force-unlocked, ran a plan: one resource needed importing... prod is clean again. u guys are the best!!!
Sign in or create an account to reply.
