inaccurate error output in snapcraft release if given invalid revision
Metadata
Current evaluation
Bug report: snapcraft release shows misleading 'No such command release' error when given an invalid revision. Untriaged, 888 days old with no maintainer interaction.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer comments, and no assignee after 888 days, indicating it has never been triaged. The bug report about a misleading error message when running `snapcraft release` with an invalid revision appears valid but requires maintainer assessment to confirm whether the issue still exists in the current codebase.
Impact:
45
Quick Win:
33.75
Staleness:
92
Complexity:
25
Confidence:
30
Support Request:
15
Issue body
We noticed in one of our release jobs an error stating "No such command 'release'", while `snapcraft release` was certainly working in the previous tasks within the same job:
```
...
19:13:41 Starting Snapcraft 7.5.5
19:13:41 Logging execution to '/home/jenkins/.local/state/snapcraft/log/snapcraft-20240329-011340.363807.log'
19:13:41 Released 'juju' revision 26908 to channels: '2.9/candidate'
19:13:41 + [[ False == \T\r\u\e ]]
19:13:41 + [[ 2.9 == \2\.\9 ]]
19:13:41 + for arch in $build_arches
19:13:41 ++ snapcraft list-revisions juju
19:13:41 ++ awk '{print $1;exit}'
19:13:41 ++ grep 2.9/candidate/strict-501fcd8
19:13:41 ++ grep ' amd64 '
19:13:46 Starting Snapcraft 7.5.5
19:13:46 Logging execution to '/home/jenkins/.local/state/snapcraft/log/snapcraft-20240329-011343.737494.log'
19:13:46 + store_revision=26909
19:13:46 ++ cat amd64.store_revision
19:13:46 cat: amd64.store_revision: No such file or directory
19:13:46 + snapcraft release juju 2.9/candidate/strict
19:13:49 Starting Snapcraft 7.5.5
19:13:49 Logging execution to '/home/jenkins/.local/state/snapcraft/log/snapcraft-20240329-011349.286474.log'
19:13:49 Usage: snapcraft [OPTIONS] COMMAND [ARGS]...
19:13:49 Try 'snapcraft -h' for help.
19:13:49
19:13:49 Error: No such command 'release'.
```
We noticed that the origin of this issue is that one of our release scripts is passing an invalid store_revision, and we're fixing that, however, along the way we noticed that if `snapcraft release` is ran with an invalid revision, we get the error messsage "No such command `release`", just wanted to raise this.
To recreate, run `snapcraft release juju "" 2.9`
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
45
Quick Win:
33.75
Staleness:
92
Complexity:
25
Confidence:
30
Support Request:
15
|
needs triage | Bug report: snapcraft release shows misleading 'No such command release' error when given an invalid revision. Untriaged, 888 days old with no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
10
|
needs triage | Reports misleading error output when snapcraft release receives an invalid revision. Untriaged, inactive for over two years, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
70
Support Request:
10
|
needs triage | Reports misleading error output when snapcraft release receives an invalid revision. Unlabeled, no maintainer response, inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | snapcraft release displays misleading No such command release error when passed an invalid revision. Untriaged, inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
25
Confidence:
85
Support Request:
5
|
needs triage | Bug report showing misleading 'No such command release' error when passing an invalid revision to snapcraft release. Untriaged and inactive for over two years. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#1664704
(confidence 60%)
Legacy Launchpad issue from 2016 about misleading error messages during snapcraft release with non-existent revisions; similar symptom but on the old CLI.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1999038 "snapcraft release" chokes given an invalid revision value | snapcraft (launchpad) | open | Issue about confusing error when 'snapcraft release' receives invalid revision. Stale for 1366 days with no maintainer response. The release command appears to have been removed or deprecated. | |
| #1664704 snapcraft release gives misleading error when revision does not exist | snapcraft (launchpad) | open | snapcraft release shows misleading error suggesting 'snapcraft register' when the real problem is a non-existent revision. Filed 2016, 0 comments, no maintainer interaction; legacy CLI since replaced by craft-based rewrite. | |
| #1604810 try to snapcraft release an unexisting revision shows the wrong error | snapcraft (launchpad) | open | Misleading error when running snapcraft release with a non-existent revision: it suggests 'snapcraft register' instead of saying the revision is invalid. Filed by maintainer elopio in 2016, labelled bitesize, 0 comments, no activity for ~9.5 years; the legacy CLI has since been replaced by the craft-based rewrite. | |
| #1665003 Poor message when failing to specify a valid version | snapcraft (launchpad) | open | Legacy snapcraft CLI showed a confusing error ('register ... before trying to release or choose an existing revision') when releasing a snap without a registered version. Reported ~9.5 years ago; no maintainer response; the current craft-based codebase no longer contains that message. |