`snapcraft clean <part>` doesn't ensure the project is mounted
Metadata
Current evaluation
Snapcraft 3.1 clean <part> fails in Multipass after manually unmounting the project; the report remains unlabelled and untriaged with no activity since submission.
Suggested action: needs triage
Reason: The report provides an exact Snapcraft 3.1 Multipass reproduction, but it has no labels, maintainer response, assignee, or follow-up activity. Current code mounts the project in prepare_instance(), while the existing clean spread test does not cover a manually unmounted instance, so applicability to the current provider flow needs triage.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
18
Complexity:
42
Confidence:
82
Actionability:
82
Issue body
With a snapcraft.yaml including 'base:':
$ snapcraft version
snapcraft, version 3.1
$ snapcraft pull
$ multipass unmount snapcraft-<project>
$ snapcraft clean <part>
Launching a VM.
Could not find snap/snapcraft.yaml. Are you sure you are in the right directory?
To start a new project, use `snapcraft init`
An error occurred when trying to execute 'sudo -i snapcraft clean <part>' with 'multipass': returned exit code 2.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
18
Complexity:
42
Confidence:
82
Actionability:
82
|
needs triage | Snapcraft 3.1 clean <part> fails in Multipass after manually unmounting the project; the report remains unlabelled and untriaged with no activity since submission. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
20
Complexity:
30
Confidence:
60
Actionability:
70
|
keep open | snapcraft clean <part> fails when project directory is unmounted from build provider, reporting missing snap/snapcraft.yaml | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
Staleness:
95
Complexity:
30
Confidence:
75
Support Request:
10
|
close stale | snapcraft clean <part> fails with 'Could not find snap/snapcraft.yaml' when the multipass project is manually unmounted. Reported in 2017 against v3.1; no maintainer response. Codebase since rewritten to craft_application, making the original code path obsolete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
95
Support Request:
10
|
close stale | Issue from 2017 reporting that snapcraft clean fails when the project directory is unmounted. No maintainer response, lacks labels, and references snapcraft v3.1. The issue is extremely outdated and irrelevant to current releases. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Bug report stating snapcraft clean <part> fails when the project directory is unmounted, causing a missing snapcraft.yaml error. Issue is over 7 years old with no maintainer response or activity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
35
Confidence:
92
Support Request:
5
|
close stale | snapcraft clean <part> fails to remount the project directory in the build environment, causing a missing snapcraft.yaml error. Unlabelled and inactive for over 7 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1690139
(confidence 55%)
Another clean-part report was closed after maintainers confirmed expected behavior, but it concerned missing cleanup files rather than an unmounted project.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1794955 snapcraft erroneously errors when deleting non-existent multipass container | snapcraft (launchpad) | open | snapcraft clean treats an absent Multipass instance as a deletion error after Multipass was reinstalled; the report is concrete but untriaged and may need validation against the current clean path. | |
| #1869542 snapcraft unable to find snap/snapcraft.yaml file | snapcraft (launchpad) | open | Snapcraft 3.11 on Multipass intermittently lost the project dir in the VM ('Could not find snap/snapcraft.yaml'), only fixable by `snapcraft clean`. Reproducer never supplied; reporter redirected it to the Multipass tracker and never followed up. | |
| #1807125 After snapcraft refresh, old multipass containers no longer work | snapcraft (launchpad) | open | Snapcraft 3.0.1 could reuse incompatible Multipass VMs after a 3.0.0 refresh, causing a misleading missing-project error until snapcraft clean; the report is untriaged. |