Improve the LXD init experience
Metadata
Current evaluation
Rockcraft should check if LXD is properly installed and configured before pack fails with cryptic messages. Core functionality implemented in craft-providers via is_initialized().
Suggested action: close resolved
Reason: The core request — checking if LXD is properly initialized before rockcraft pack — has been implemented in craft-providers via the is_initialized() function (commit a6b11b5c). Comment from @cjdcordeiro confirms 'This is already in'. craft-providers#436 was merged to require a disk device in the default LXD profile, and craft-providers#588 (addressing broken profile edge cases) was closed as obsolete by the maintainer. The remaining improvements mentioned (profile updates, multi-profile selection) are enhancements beyond the original scope.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
20
Complexity:
30
Confidence:
75
Actionability:
70
|
close resolved | Rockcraft should check if LXD is properly installed and configured before pack fails with cryptic messages. Core functionality implemented in craft-providers via is_initialized(). | |
| stealth/space-bunny-alpha |
Impact:
46
Quick Win:
24
Complexity:
38
Confidence:
96
Actionability:
84
|
close resolved | Rockcraft now receives actionable preflight checks for LXD installation and initialization through craft-providers; residual profile-selection ideas are optional follow-ups. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
11
Complexity:
40
Confidence:
70
Actionability:
60
|
keep open | Feature request to improve LXD init experience in rockcraft, including LXD configuration checks and profile management. Some work done but specific improvements remain unresolved. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
15
Staleness:
55
Complexity:
40
Confidence:
75
Support Request:
10
|
keep open | LXD init check for rockcraft pack is implemented in craft-providers. Maintainer kept issue open for two follow-ups: handling broken LXD profiles from older versions (PR #588 closed unmerged) and multi-profile selection. Inactive ~12.5 months. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
20
|
keep open | Feature request to improve LXD initialization checks in Rockcraft. Core implementation is complete, but maintainers noted open follow-ups for handling broken LXD profiles and multi-profile selection. Currently inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
0
|
close stale | Request to improve LXD initialization checks in Rockcraft. Core functionality appears implemented, but follow-up enhancements for legacy broken profiles were discussed. Last active 10 months ago with no concrete next steps. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
50
Confidence:
75
Support Request:
15
|
close stale | Rockcraft should verify LXD is initialized before building. Core check is implemented, but discussion remains on handling legacy broken profiles and profile selection. Open for ~2 years with recent maintainer comments. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-providers#436
(confidence 80%)
Merged PR that requires a disk device in the default LXD profile, addressing profile validation
-
Likely Fixed By:
canonical/craft-providers#588
(confidence 60%)
Closed as obsolete by maintainer; addressed broken profile handling from older Rockcraft versions
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #63 lxd: check if LXD is initialized prior to launch (CRAFT-348) | craft-providers | merged | Merged LXD initialization preflight validation for CRAFT-348, adding is_initialized(), launch-time LXDError handling, and unit/integration tests in commit b00bea0. | |
| #474 charmcraft: perform LXD checks before use (CRAFT-420) | charmcraft | merged | Merged #474: added ensure_lxd_is_ready() before LXD use, including permission validation and clearer errors. Merge commit: 1dfb54b1. |