← Back to issue list

snapcraft push fails to a registered name

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1691597
Type
issue
State
closed
Author
~cprov
Labels
—
Created
Updated
Closed

Current evaluation

Merged PR #2749 (commit ac2d48293) improved store error handling with StoreErrorList and clearer StorePushError output for forbidden and missing resources.

Resolution: closed resolved

Reason: The confusing push failure was resolved by merged PR #2749 in commit ac2d48293, which added structured handling for resource-not-found and resource-forbidden store responses.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Initial `snapcraft push` to a registered name is failing: {{{ $ snapcraft registered Name Since Visibility Price Notes hello-robinhood2017 2017-05-17T16:15:08Z public - - $ snapcraft push hello-robinhood2017_2.10_amd64.snap Starting snapcraft 2.29+17.4 from /usr/lib/python3/dist-packages/snapcraft. b'Parallel unsquashfs: Using 2 processors\n1 inodes (1 blocks) to write\n\n\r[===================================================================|] 1/1 100%\n\ncreated 1 files\ncreated 2 directories\ncreated 0 symlinks\ncreated 0 devices\ncreated 0 fifos\n' Preparing to push 'hello-robinhood2017_2.10_amd64.snap' to the store. Starting new HTTPS connection (1): myapps.developer.ubuntu.com "POST /dev/api/snap-push/ HTTP/1.1" 200 None Starting new HTTPS connection (1): upload.apps.ubuntu.com ] 0% "POST /unscanned-upload/ HTTP/1.1" 200 None [============================ ] 99% Pushing hello-robinhood2017_2.10_amd64.snap [=============================] 100% Starting new HTTPS connection (1): myapps.developer.ubuntu.com "POST /dev/api/snap-push/ HTTP/1.1" 202 None Starting new HTTPS connection (1): dashboard.snapcraft.io "GET /dev/api/snaps/mVyGrEwiqSi5PugCwyH7WgpoQLemtTd6/builds/ba76f29c-ff83-4d0f-9890-f4ae0b87f178/status HTTP/1.1" 200 69 Starting new HTTPS connection (1): dashboard.snapcraft.io "GET /dev/api/snaps/mVyGrEwiqSi5PugCwyH7WgpoQLemtTd6/builds/ba76f29c-ff83-4d0f-9890-f4ae0b87f178/status HTTP/1.1" 200 167 Processing...| Error while processing... Traceback (most recent call last): File "/usr/bin/snapcraft", line 31, in <module> snapcraft.main.main() File "/usr/lib/python3/dist-packages/snapcraft/main.py", line 253, in main return run(args, project_options) File "/usr/lib/python3/dist-packages/snapcraft/main.py", line 297, in run _run_store_command(args) File "/usr/lib/python3/dist-packages/snapcraft/main.py", line 365, in _run_store_command snapcraft.push(args['<snap-file>'], release_channels) File "/usr/lib/python3/dist-packages/snapcraft/_store.py", line 455, in push result = _push_snap(snap_name, snap_filename) File "/usr/lib/python3/dist-packages/snapcraft/_store.py", line 477, in _push_snap tracker.raise_for_code() File "/usr/lib/python3/dist-packages/snapcraft/storeapi/__init__.py", line 790, in raise_for_code raise errors.StoreReviewError(self.__content) snapcraft.storeapi.errors.StoreReviewError: The store was unable to accept this snap. - __all__: You do not have access to modify this package. }}}

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged PR #2749 (commit ac2d48293) improved store error handling with StoreErrorList and clearer StorePushError output for forbidden and missing resources.
stealth/space-bunny-alpha — closed resolved Resolved by merged PR #2749, which improved store error handling for push failures involving inaccessible or mismatched snap names.
stealth/space-bunny-alpha — closed stale Closed as stale after the identical report was closed without resolution due to inactivity; no fix or follow-up was recorded.
qwen/qwen3.6-35b-a3b — — Closed without resolution due to inactivity. The report detailed a snapcraft push failure returning a StoreReviewError for lacking package modification access. No fix or follow-up comments were provided.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The push failure resulted from a permissions error denying access to the registered package. Likely abandoned or rejected due to user ownership conflicts or tool obsolescence.
qwen/qwen3.6-35b-a3b — — Closed due to insufficient permissions. The push failed with a StoreReviewError indicating lack of access rights to modify the registered snap. Resolved by correcting account permissions or closed as invalid.
qwen3.6-35b-a3b-mtp-q6 — — Abandoned and closed without resolution. The push failed with a StoreReviewError indicating insufficient permissions to modify the registered package. No fix or workaround was provided.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#2749 (confidence 97%)

    The merged PR added StoreErrorList and improved StorePushError handling for the resource errors encountered during push.

  • Related To: snapcore/snapcraft#2749 (confidence 95%)

    Follow-up commit ff0682ca1 refined the change to use only errors with codes in StoreErrorList.

Related issues

Issue Project State Summary Similarity
#1761488 snapcraft 2.39.2 failed to release a snap: snapcraft.storeapi.errors.StoreReleaseError: <exception str() failed> snapcraft (launchpad) closed Root cause was Mozilla-side (passing a string instead of a list of channels to _store.push); Snapcraft's unprintable StoreReleaseError was fixed by commit ef350b47 and PR #2056 (merged as 1f90b2a9), shipped in 2.41.
71%
#1009 store: implement push pre-check. snapcraft merged Merged PR #1009 as commit 8d7b53aa3, adding a store pre-check so `snapcraft push` reports unregistered snaps before uploading (LP: #1610776).
71%