LXC mount rewrite treats pre-marker MXC mounts as operator-owned, so stale bind mounts survive a policy change

[dhoehna]

Containers provisioned before the # mxc-managed-mount marker existed carry unmarked MXC mounts, and src/backends/lxc/common/src/lxc_bindings.rs treats those as operator-owned and leaves them mounted.

[github-actions]

Triage summary

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

This is a correctness bug in the LXC mount-entry ownership logic: containers provisioned before the # mxc-managed-mount marker was introduced (commit 1832e437) have no marker above their lxc.mount.entry lines, so replace_mxc_mount_entries / strip_mxc_mount_entries treats all existing MXC-added mounts as operator-owned and skips them, leaving stale bind mounts alive even after a policy change.

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 #886 · sonnet46 · 24.7 AIC · ⌖ 4.15 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.