LXC provision can race lxc-create because the lifecycle lock is a no-op when the LXC root is absent

[dhoehna]

src/backends/lxc/common/src/state_aware.rs returns an unlocked guard when the LXC root is missing, so two provisions can race lxc-create.

[github-actions]

Triage applied:

• Labels: OS-Linux, Area-Executor-LXC
• Assigned: @SohamDas2021 (Linux / LXC owner)

The issue describes a concurrency bug in LifecycleLock::acquire (src/backends/lxc/common/src/state_aware.rs) where two concurrent provision calls can both receive unlocked guards when the LXC root directory doesn't yet exist, allowing both to race lxc-create.

Maintainers: Comment /investigate to check whether this issue or bug is valid against the most current code. Copilot will also produce a report with the changes that will be needed. For a small, unambiguous documentation or test fix, it may also create one draft PR.

Generated by 🏷️ Issue Triage for #880 · sonnet46 · 24.5 AIC · ⌖ 5.46 AIC · ⊞ 7.4K · ◷

[dhoehna]

Consolidated into #899 -- [LXC] State-aware lifecycle: provision, adopt, and config-rewrite races.

The backlog now carries one issue per area instead of one per finding. This report is reproduced there in full and unedited; nothing here is dropped. Track and fix it at #899.

[github-actions]

This issue was already closed and has labels OS-Linux and Area-Executor-LXC applied. No additional triage actions were needed — the issue is correctly categorized for the LXC backend on Linux.

Generated by 🏷️ Issue Triage for #880 · sonnet46 · 13.8 AIC · ⌖ 5.21 AIC · ⊞ 7.4K · ◷