Odd behaviour with parallel snapcraft installs
Metadata
Current evaluation
Closed as unreproducible: maintainer could not reproduce parallel-install failure after experimental.parallel-instances was re-set; reporter pointed to a snapd bug, filed as LP bug #2111940.
Resolution: closed not a bug
Reason: mr-cal provided a reproducible multipass script and found no failure; dilyn-corner confirmed that once experimental.parallel-instances was set again the error vanished, concluding the root cause is snapd allowing parallel installs without the feature flag (LP bug #2111940). No Snapcraft code change was made, and earlier parallel-install reports (#4683, #4927) were already fixed by PRs #5085/#5087.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed as unreproducible: maintainer could not reproduce parallel-install failure after experimental.parallel-instances was re-set; reporter pointed to a snapd bug, filed as LP bug #2111940. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as unconfirmed; Snapcraft could not reproduce the parallel-install failure after the flag was re-enabled. The reporter identified a possible snapd cause and filed LP bug #2111940. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as unconfirmed. The reporter could not reproduce the error after re-enabling the parallel instances flag. Concluded snapd mishandles disabled parallel installs and filed a separate snapd bug report. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as unconfirmed. The reported parallel install failure traced to a disabled experimental feature flag. Unable to reproduce after re-enabling it, the issue was abandoned and attributed to a snapd configuration oversight. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as not reproducible. Traced to snapd failing to enforce the parallel-instances experimental flag. Unable to reproduce after re-enabling it. Filed as upstream snapd bug #2111940. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4683
(confidence 70%)
Prior parallel-install issue (non-aliased version missing) already fixed by PRs #5085/#5087; reporter linked it as reminiscent
-
Related To:
canonical/snapcraft#4927
(confidence 70%)
Prior parallel-install bug (snapcraft not passed to LXD instance) fixed by PR #5085 and backport #5087
-
Superseded By:
snapd#2111940
(confidence 60%)
Launchpad snapd bug #2111940 filed by reporter: snapd should not allow parallel installs when experimental.parallel-instances is unset
-
Likely Fixed By:
canonical/snapcraft#5085
(confidence 45%)
Earlier fix passing the running (possibly parallel) snapcraft into managed instances; regression could stem from there
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1985409 snapcraft-managed lxd containers do not respect parallel installs | snapcraft (launchpad) | closed | Reported 2022 that parallel-installed snapcraft instances (e.g. snapcraft_7) launch the unsuffixed host snapcraft inside their managed LXD build container, causing '--build-for' build failures. Closed in 2026 after PR #5085 and 7.5 backport #5087. | |
| #411 Support snap parallel installs | craft-application | closed | Parallel-installed snap injection was fixed by PR #467 (commit 77a3582b); #411 was closed as fixed, with a separate craft-providers gap noted. |