← Back to issue list

remote build: internal error from 400 response

View original Github issue

Metadata

Project
snapcraft
Number
#5517
Type
issue
State
open
Author
mr-cal
Labels
Status: Triaged Type: Bug
Created
Updated
Closed
—

Current evaluation

Snapcraft remote build exposes an internal error when Launchpad returns a 400 (BadRequest) during repo push; the lazr.restfulclient.errors.BadRequest exception is not caught. Triaged as a bug, fix likely needed upstream in Craft Application.

Suggested action: keep open

Reason: The issue is labelled Status: Triaged and Type: Bug, with a Jira ticket (SNAPCRAFT-1143) created, indicating it has been assessed and acknowledged by maintainers. The underlying problem — an uncaught `lazr.restfulclient.errors.BadRequest` during repo push to Launchpad — is a real bug that exposes internal errors to users. No evidence of a fix has been found in either the snapcraft or craft-application repositories, so the issue remains open and valid. The 461-day age with no further activity suggests it is moderately stale but not irrelevant.

Impact: 50 Quick Win: 30.0 Staleness: 70 Complexity: 40 Confidence: 60 Support Request: 10

Issue body

### What needs to get done Catch and raise a user-friendly error when Snapcraft fails to push a repo to Launchpad. This likely needs to be fixed upstream in Craft Application. We already catch many `launchpadlib` errors but `lazr.restfulclient.errors.BadRequest` isn't being caught when pushing the repo. ### Why it needs to get done To provide a better UX. Internal errors should never be exposed. Source: - @jnsgruk via [matrix](https://matrix.to/#/!fcfzhmtmKApekMQcxX:ubuntu.com/$i_-XIB1IDWrY4w7j16LkWR9-9JFwtVsPv4t65wpbsgg?via=ubuntu.com&via=matrix.org) - [snapcraft-20250527-114721.927489.log](https://github.com/user-attachments/files/20458454/snapcraft-20250527-114721.927489.log)

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 50
Quick Win: 30.0
Staleness: 70
Complexity: 40
Confidence: 60
Support Request: 10
keep open Snapcraft remote build exposes an internal error when Launchpad returns a 400 (BadRequest) during repo push; the lazr.restfulclient.errors.BadRequest exception is not caught. Triaged as a bug, fix likely needed upstream in Craft Application.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 30
Confidence: 90
Support Request: 10
keep open Tracks catching and handling lazr.restfulclient.errors.BadRequest during Launchpad repo pushes to prevent internal errors. Currently triaged and awaiting implementation.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 75
Support Request: 0
keep open Valid bug report requesting better error handling for Launchpad push failures. Triaged but inactive for over a year with no upstream fix or maintainer follow-up.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 80
Support Request: 0
keep open Catch unhandled Launchpad BadRequest errors during remote builds to prevent internal errors and improve UX. Triaged bug awaiting implementation or upstream Craft Application fix. Internal Jira ticket SNAPCRAFT-1143 created.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#4783 remote build: fail if launchpad fails to create artifacts snapcraft closed Fixed via #4826. Snapcraft remote-build now exits with an error when Launchpad fails to produce artifacts due to architecture mismatches, replacing the previous silent success with explicit failure reporting and validation.
71%
#5960 remote build: internal error when build is cancelled on launchpad snapcraft open Remote build crashes with MissingSchema when a build is cancelled on Launchpad: fetch_logs tries to download a log URL that is the string 'None'. Triaged by maintainer, upstream fix tracked in craft-application#996.
70%