← Back to issue list

`snapcraft clean <part>` doesn't ensure the project is mounted

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1813942
Type
issue
State
open
Author
~saviq
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: close stale

Reason: The issue is 2770 days old with zero maintainer interaction. The snapcraft codebase has been completely rewritten to use the craft_application framework (current CleanCommand at snapcraft/commands/lifecycle.py:153 is a thin subclass of craft_application.commands.lifecycle.CleanCommand), so the specific multipass mount-handling code path described in the 2017 report no longer exists. The reproduction also requires manually running 'multipass unmount', an unusual edge case unlikely to affect normal workflows.

Impact: 20 Quick Win: 14.0 Staleness: 95 Complexity: 30 Confidence: 75 Support Request: 10

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
qwen/qwen3.8-27b
Impact: 20
Quick Win: 14.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 99
Complexity: 20
Confidence: 95
Support Request: 5
close stale snapcraft clean <part> fails when the project directory is unmounted in the build VM, throwing a missing snapcraft.yaml error. The command lacks mount verification. Open, unassigned, inactive for over seven years, requires triage.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1826262 Error: The part has run through its entire lifecycle snapcraft (launchpad) open Snapcraft 1.x build error 'part has run through its entire lifecycle' reported in 2017 when modifying multipass snapcraft.yaml; zero comments, no labels, project since fully rearchitected into craft-* subprojects.
74%
#1807125 After snapcraft refresh, old multipass containers no longer work snapcraft (launchpad) open snapcraft reuses outdated multipass containers after snap refresh, causing 'Could not find snap/snapcraft.yaml' errors until snapcraft clean is run; untriaged, no maintainer activity for ~7.7 years
70%