Misleading error message about lxd.migrate
Metadata
Current evaluation
A false-positive LXD deb-package warning blocked Snapcraft despite the LXD snap being installed; the maintainer planned to remove the check, but the issue remains open.
Suggested action: close stale
Reason: The reporter confirmed that removing the transitional deb package bypassed the warning, and maintainer @~cjp256 explicitly said the deb check would be removed. This old --use-lxd path has since been superseded by craft-providers, where the warning, lxd.migrate, and lxd-client checks no longer exist, making the affected implementation obsolete.
Evaluated by: mr-cal-bot
Impact:
35
Quick Win:
27
Complexity:
12
Confidence:
96
Actionability:
88
Issue body
Running `snapcraft --use-lxd` on my Ubuntu 20.04 system led to this error:
The 'LXD' provider does not support having the 'lxd' or 'lxd-client' deb packages installed. To completely migrate to the LXD snap run 'lxd.migrate' and try again.
Even though I knew my lxd was already coming from the snap version, I ran `lxd.migrate` anyway, and it failed:
=> Connecting to source server
error: Unable to connect to the source LXD: Get "http://unix.socket/1.0": dial unix /var/lib/lxd/unix.socket: connect: no such file or directory
Running out of ideas, I removed the transitional deb package for lxd, and that indeed solved the issue. But maybe snapcraft should either make the message more clear, or the lxd.migrate tool (or even snapcraft itself) should be made smarter and just check if the lxd snap is installed, without caring about the deb version.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
27
Complexity:
12
Confidence:
96
Actionability:
88
|
close stale | A false-positive LXD deb-package warning blocked Snapcraft despite the LXD snap being installed; the maintainer planned to remove the check, but the issue remains open. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
28
Complexity:
12
Confidence:
92
Actionability:
90
|
close resolved | Snapcraft's old LXD provider incorrectly advised running lxd.migrate when a transitional lxd deb was installed; the legacy check and message have since been removed. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
9
Complexity:
40
Confidence:
60
Actionability:
50
|
close resolved | Misleading error message about lxd.migrate when LXD snap is already installed; issue is ~5.4 years old with no maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
19
Staleness:
90
Complexity:
25
Confidence:
60
Support Request:
15
|
close stale | Snapcraft's LXD provider error message tells users to run lxd.migrate when the real fix is removing the transitional lxd deb package. Reported on Ubuntu 20.04; no maintainer response in ~5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | User reports a misleading snapcraft error message regarding LXD and suggests improving lxd.migrate. The issue lacks labels, has zero maintainer interaction, and has been inactive for over 5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
0
|
close stale | Reports a misleading snapcraft error message regarding LXD migration and suggests improving the lxd.migrate tool to detect existing snap installations. Unaddressed for nearly five years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
75
Support Request:
10
|
close stale | Misleading snapcraft error suggests running lxd.migrate even when LXD snap is installed. Suggests improving error messaging or migration logic. Inactive for over 5 years with no maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1728649 LXD not running error message is vague | snapcraft (launchpad) | closed | Enhancement request to improve the vague "Connection refused; is LXD running?" error from `snapcraft cleanbuild`. Discussion stalled over whether to recommend purging the apt lxd package; closed incomplete and later expired by Launchpad janitor with no code change. |