redhat-developer / redhat-developer/mapt
[bug] If create operation ends up unexpectedly it creates a lock and destroy is not working
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
To solve this issue we can create a flag --force on the destroy operation to force remove the lock before running the destroy.
Hint: check how that would work on remote backed url
{"level":"error","msg":"failed to refresh stack: exit status 255\ncode: 255\nstdout: \nstderr: 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`.\n file:///workspace/.pulumi/locks/organization/windows-desktop/stackCreateWindowsDesktop-windows-desktop/ce397a2f-81f2-416a-9311-dbb93c9b9e6a.json: created by root@a75f5d17663b (pid 46) at 2023-12-04T15:55:41Z\n\n","time":"2023-12-04T16:04:53Z"}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the destroy operation and its handling of locks, then compare local and remote-backed URL behavior as suggested in the issue. Confirm the failure using the provided locked-stack scenario; done means a force option removes the lock and allows destroy to proceed without the current lock error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100