lxc: use only instance lxc lock when creating
Metadata
Current evaluation
Merged PR #386 fixed LXC creation locking so only the selected instance's LXC lock is used, preventing cross-instance lock and etag race failures.
Resolution: closed resolved
Reason: PR #386 was approved and merged into main as commit 277933d. The change ensures creation is serialized by the instance's own LXC lock, resolving the etag race caused by locks from separate LXC instances.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #386 fixed LXC creation locking so only the selected instance's LXC lock is used, preventing cross-instance lock and etag race failures. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #386 in commit 277933d, making LXC creation use the instance lock to prevent concurrent etag errors. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR #386 which resolves LXC locking issues by ensuring only the instance lxc lock is used when creating, fixing etag errors from multiple LXC class instances. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.