boundless-potato-4457407/16/2023, 11:31 PM
live, and delete them manually if push comes to shove. Today, however, my Github action that runs pulumi up (and has done so historically) is throwing an error after some rough treatment (
with some GUI interference).
And finally the puzzle: there is NO file at that URL. In fact, the entire locks directory is absent (as it usually is when there are no locks). This error is persisting even after
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`. <gs://mybucket//.pulumi/locks/test/33cd4732-e6ea-4e4f-a901-12777979d41a.json>: created by runner@fv-az267-906 (pid 2144) at 2023-07-16T18:45:19Z
and I’m at my wit’s end! Has anyone seen this behavior before? Has anyone figured out how to get past it? Maybe resetting the stack some other way, or forcing the github action to refresh its cache? Thanks!
2. Copy/paste/rename it to match the phantom lock 3. Complete the refresh 4. Finally
to delete the fake lock (NB the URL is slightly different) Voila! The 👻 is gone!
gsutil rm <gs://mybucket/.pulumi/locks/test/33cd4732-e6ea-4e4f-a901-12777979d41a.json>