← Back to issue list

snapcraft validate does not work with snaps in stores other than Global

View original Launchpad issue

Metadata

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

Current evaluation

Fixed by snapcore/snapcraft PR #3349 (commit 1fc64e4ac, "cli: allow snap-id for validate"), which lets validate accept snap IDs directly instead of only resolving names via the Global store; released in snapcraft 4.4.1.

Resolution: closed resolved

Reason: The reporter identified StoreClientCLI.get_info as unable to resolve snaps outside the Global store and proposed accepting explicit snap IDs. PR snapcore/snapcraft#3349 (commit 1fc64e4ac) implemented that; maintainer Sergiusens noted "Released in 4.4.1", and validations.py now documents both `<snap-name>=<revision>` and `<snap-id>=<revision>` syntax.

Evaluated by: mr-cal-bot

No scores available.

Issue body

A customer is trying to issue a validation assertion using snapcraft, and one of the snaps being added as gated snap is not available in public searches. So when running, for example, the following command: nessita@dali:~$ snapcraft validate nessita-gating snapd=1255 caracalla-kernel=136 --key-name=validations-test Getting details for snapd Signing validations assertion for snapd=1255 Getting details for caracalla-kernel Snap 'caracalla-kernel' was not found. Recommended resolution: Ensure you have proper access rights for 'caracalla-kernel'. I can't issue the validation though my account does have access to that snap.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed by snapcore/snapcraft PR #3349 (commit 1fc64e4ac, "cli: allow snap-id for validate"), which lets validate accept snap IDs directly instead of only resolving names via the Global store; released in snapcraft 4.4.1.
stealth/space-bunny-alpha — closed resolved Fixed by snapcore/snapcraft PR #3349 (commit 1fc64e4ac), allowing validate to fall back to explicit snap IDs for private or non-global snaps; released in snapcraft 4.4.1.
stealth/space-bunny-alpha — closed resolved snapcraft validate could not resolve gated snaps outside the Global store. Fixed by PR #3349 (commit 1fc64e4ac "cli: allow snap-id for validate"), which lets validate accept snap IDs directly; released in snapcraft 4.4.1.
stealth/space-bunny-alpha — closed resolved Fixed by PR #3349 (commit 1fc64e4ac "cli: allow snap-id for validate"), which lets validate accept snap IDs instead of searching the Global store; shipped in snapcraft 4.4.1.
stealth/space-bunny-alpha — closed stale Closed with no recorded fix, explanation, or linked PR/commit; Snapcraft validation with non-Global-store snaps was not shown to be resolved.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The snapcraft validate failure for non-global store snaps was abandoned due to inactivity, with no fix implemented or workaround provided.
qwen/qwen3.6-35b-a3b — — Closed without resolution due to inactivity. The snapcraft validate command failed to locate snaps in non-global stores despite proper user access. No fix was implemented.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#3349 (confidence 95%)

    Cited by maintainer as the fix; commit 1fc64e4ac 'cli: allow snap-id for validate'.

  • Related To: snapcraft (launchpad)#1775658 (confidence 80%)

    Reported by the same author as the sibling limitation: get_info also fails for snaps never released to stable.

Related issues

Issue Project State Summary Similarity
#3349 cli: allow snap-id for validate snapcraft merged Merged PR #3349 (commit 1fc64e4ac, LP #1902913) lets `snapcraft validate` accept a snap-id as fallback when the Info API can't resolve a name, e.g. for private snaps; shipped on edge/pr-3349.
71%