https://pulumi.com logo
Join Slack
Powered by
Update: Issue is due to a new bug in Bitbucket pi...
# general
c
Update: Issue is due to a new bug in Bitbucket pipelines I need help debugging a strange issue where my CI/CD system is now failing because of spurious lock files on the s3 state backing:
Copy code
Logged in to df6cb4fba5de as root (s3://....)
pulumi stack select dev
error: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or delete the lock file with `pulumi cancel`.
  s3://...: created by root@c232aa577335 (pid 466) at 2025-10-24T06:13:03Z
Searching for test report files in directories named [test-reports, surefire-reports, failsafe-reports, test-results, TestRes
I even added a 
pulumi cancel -y
to the pipeline but it still hits the locking failure:
Copy code
make login-$STACK &&
pulumi cancel -y &&
pulumi up -y -f
pulumi login 's3://...'
Logged in to f0ef7c8e5c60 as root (s3://...)
pulumi stack select dev
The currently running update for 'dev' has been canceled!
error: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or delete the lock file with `pulumi cancel`.
  s3://...: created by root@e921618df966 (pid 476) at 2025-11-28T04:56:45Z
This bitbucket pipeline is configured to pull pulumi:latest and started failing on October 24th -- I tried pulling the versions prior to Oct 24th 
3.203.0
but am still running into this problem. That said, I have not found other people with the same problems on Github issues. I do, however, want to debug this further before creating a Github issue; does anyone have advice on how I can debug this problem further?
I am also looking into if the Bitbucket pipeline itself is causing this problem somehow, but that's another thread on another forum...
e
For one you cancel call looks like its happening before the login call, so it probably isn't cancelling anything. If you flip that so you login, then select, then cancel, then run up does it help?
c
The 
pulumi cancel
call is performed after login/stack selection -- this is just a quirk of the Bitbucket pipeline output.
I did more troubleshooting and discovered this is a Bitbucket pipeline bug... they began executing pipeline script tasks twice on Oct 24th causing a race condition for 
pulumi up
operations. Closing my request for help here 👍
e
ah good to know
40 Views
Open in Slack
PreviousNext
Powered by