LXD integration tests incompatible with canonical/setup-lxd
Metadata
Current evaluation
Old request to make LXD integration tests work with canonical/setup-lxd user/group permissions. The tests.yaml workflow that motivated it was deleted (b2b9b81) and CI moved to Starflow, making the request obsolete.
Suggested action: close stale
Reason: The specific file the issue links to (.github/workflows/tests.yaml, with its `runs-on`-as-`lxd`-user step) no longer exists: commit b2b9b81 'ci: remove old test workflow' deleted it, confirmed by git_log_path returning that commit as the most recent touch. CI has since been migrated to canonical/starflow -- qa.yaml calls canonical/starflow/.github/workflows/test-python.yaml@main with `use-lxd: true` and pytest-markers `lxd_instance`, and tests-weekly.yaml uses canonical/starflow/setup-python-runner with a `lxd-channel` input. No reference to setup-lxd remains anywhere in the repo (grep returns no matches). The maintainer's own closing comment ('I played around with this and haven't had luck') plus the group/permission dead-end they describe (newgrp lxd not working non-interactively, inability to cycle login) indicates this was never a craft-providers code defect but a harness-placement problem now superseded by Starflow. The ask is obsolete rather than merely stale by age.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
8
Quick Win:
1
Complexity:
15
Confidence:
88
Actionability:
20
|
close stale | Old request to make LXD integration tests work with canonical/setup-lxd user/group permissions. The tests.yaml workflow that motivated it was deleted (b2b9b81) and CI moved to Starflow, making the request obsolete. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
4
Complexity:
66
Confidence:
94
Actionability:
42
|
close stale | LXD integration tests conflict with canonical/setup-lxd group permissions; the affected legacy workflow was removed and CI migrated to Starflow, making the compatibility request obsolete. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
20
Quick Win:
14
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | LXD integration tests fail with canonical/setup-lxd due to user/group permissions. The legacy CI workflow causing this was removed and replaced with starflow workflows, making this issue obsolete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
45
Confidence:
80
Support Request:
10
|
close stale | LXD integration tests fail when using canonical/setup-lxd GitHub Action due to user/group permission mismatches. Author investigated but hit CI runner limitations; issue remains unresolved after ~3 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | LXD integration tests fail with canonical/setup-lxd due to user/group permission mismatches. Open for over three years with no maintainer response or resolution. |
Update history
No update history recorded yet.
Related work
-
Related To:
craft-providers#270
(confidence 70%)
Companion issue 'LXD integration tests fail on Ubuntu 22.04'; same LXD CI group/permission root cause discussed in mr-cal's comment here.
-
Related To:
craft-providers#222
(confidence 60%)
'lxd integration tests run `sudo lxd init`' touches the same LXD test setup area.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #863 Fix LXD integration test failures by configuring required remotes | craft-providers | closed | PR #863 was closed unmerged after its LXD remote fixture in commit 6c22337 still failed Linux integration and CLA checks; no main-branch resolution was found. |