snapcraft remote-build for a non-existent user gives me a 500 error
Metadata
Current evaluation
Resolved by merged PR #2825, which removed --launchpad-user and derives the username from the authenticated Launchpad session; included in Snapcraft 3.10.
Resolution: closed resolved
Reason: PR #2825 removed the error-prone --launchpad-user option and used the authenticated Launchpad identity instead. The change was merged and released as part of Snapcraft 3.10.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Having authed as doismellburning, I then:
```
$ snapcraft remote-build --launchpad-user devnull
<snip>
Sorry, an error occurred in Snapcraft:
HTTP Error 500: Internal Server Error
Response headers:
---
-content-encoding: gzip
connection: close
content-length: 147
content-type: text/html;charset=utf-8
date: Wed, 13 Nov 2019 19:44:25 GMT
server: zope.server.http (HTTP)
status: 500
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---
b'<html><head><title>GitRepositoryCreatorNotOwner</title></head>\n<body><h2>GitRepositoryCreatorNotOwner</h2>\nA server error occurred.\n</body></html>\n'
---
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]: no
You can find the traceback in file '/tmp/tmpmfb2bc63/trace.txt'.
```
I would expect a nice user-facing error message from snapcraft (and a better response from Launchpad than a 500)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR #2825, which removed --launchpad-user and derives the username from the authenticated Launchpad session; included in Snapcraft 3.10. | |
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft removed the error-prone --launchpad-user option and now derives the Launchpad username from the authenticated session. Implemented in snapcore/snapcraft#2825 and released in Snapcraft 3.10. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR #2825, which removed --launchpad-user and derives the username from the authenticated Launchpad session; the change was included in Snapcraft 3.10. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a documented fix; matching Launchpad bug snapcraft/launchpad#1852482 received no comments or follow-up. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report of a 500 error for non-existent Launchpad users in snapcraft remote-build received no comments or follow-up, indicating it was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned due to inactivity. The report detailed a 500 error when using a non-existent Launchpad user with snapcraft remote-build. No fix or follow-up was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. No discussion or fix was implemented. The 500 error when specifying a non-existent Launchpad user was not addressed and the issue appears abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Reported a 500 error when using a non-existent Launchpad user with snapcraft remote-build, requesting better error handling. Closed without a fix or follow-up comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2825
(confidence 99%)
Merged PR linked from the issue; released in Snapcraft 3.10.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4783 remote build: fail if launchpad fails to create artifacts | snapcraft | closed | Remote-build silently succeeded when Launchpad produced no artifacts. Fixed by merged PR #4826 (commit 552897340), which makes snapcraft remote-build fail when no artifacts are created. |