← Back to issue list

`UBUNTU_STORE_AUTH_DATA_FILENAME` should be passed from Snapcraft to SnapD during build

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2060820
Type
issue
State
open
Author
~jordanmg13
Labels
—
Created
Updated
Closed
—

Current evaluation

Snapcraft 7 reportedly failed to download an authenticated store snap during an LXD destructive build until an absolute credentials path was passed to snapd; no current reproducer exists.

Suggested action: needs triage

Reason: The issue remains unlabeled and the maintainer's questions were answered, but only indirectly: the reporter says the failure occurred in LXD destructive mode and was fixed by passing an absolute credentials path, without a minimal project or logs. Repository history and the current tree contain no UBUNTU_STORE_AUTH_DATA_FILENAME handling or resolving commit, so implementation scope needs investigation rather than closure.

Evaluated by: mr-cal-bot

Impact: 46 Quick Win: 10 Complexity: 55 Confidence: 78 Actionability: 48

Issue body

Couldn’t access a snap while building another snap with Snapcraft 7. After a while, the UBUNTU_STORE_AUTH_DATA_FILENAME parameter that was needed during the build process was discovered and worked afterwards. Therefore, we should include UBUNTU_STORE_AUTH_DATA_FILENAME during the build process for SnapD if present.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 46
Quick Win: 10
Complexity: 55
Confidence: 78
Actionability: 48
needs triage Snapcraft 7 reportedly failed to download an authenticated store snap during an LXD destructive build until an absolute credentials path was passed to snapd; no current reproducer exists.
stealth/space-bunny-alpha
Impact: 46
Quick Win: 9
Complexity: 52
Confidence: 74
Actionability: 42
needs triage Snapcraft 7 failed to install an authenticated store snap during an LXD/destructive build until snapd received an absolute credentials path via UBUNTU_STORE_AUTH_DATA_FILENAME; no current reproducer exists.
stealth/space-bunny-alpha
Impact: 42
Quick Win: 11
Complexity: 46
Confidence: 87
Actionability: 48
needs triage Snapcraft 7 reportedly cannot access a snap needed during another snap’s build. Forwarding an existing store-authentication filename may fix it, but no reproducer or maintainer triage is recorded.
qwen3.6-35b-a3b-mtp-q6
Impact: 55
Quick Win: 30
Staleness: 90
Complexity: 45
Confidence: 50
Support Request: 35
close stale Feature request to pass UBUNTU_STORE_AUTH_DATA_FILENAME env var from Snapcraft to SnapD during builds. Untriaged, 876 days old with no maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 35
Support Request: 10
needs triage Suggests passing UBUNTU_STORE_AUTH_DATA_FILENAME from Snapcraft to SnapD during builds to resolve snap access issues. Unlabelled, no maintainer response, inactive for over 2 years.
qwen/qwen3.6-35b-a3b
Staleness: 90
Complexity: 15
Confidence: 85
Support Request: 10
needs triage Suggests passing UBUNTU_STORE_AUTH_DATA_FILENAME from Snapcraft to SnapD during builds to resolve snap access issues. Untriaged, inactive for over two years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 10
close stale Request to automatically pass UBUNTU_STORE_AUTH_DATA_FILENAME from Snapcraft to SnapD during builds. Untriaged and inactive for over two years with no maintainer response.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1802327 (confidence 84%)

    Open issue reports that private build snaps cannot be used during builds, matching the reported symptom.

Related issues

No related issues found above the similarity threshold.