lxd: ContainerConnectionError on failed launch/ start
Metadata
Current evaluation
Superseded by #1771, merged as 1a7a4f7d0 to suppress tracebacks when LXD launch/init fails.
Resolution: closed superseded
Reason: Maintainer sergiusens closed this PR in favor of #1771, which was subsequently merged in commit 1a7a4f7d0.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)?
- [x] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)?
- [x] Have you successfully run `./runtests.sh static`?
- [x] Have you successfully run `./runtests.sh unit`?
-----
Currently if LXD fails to launch one still ends up with a backtrace w/o the --debug switch, eg.:
Creating snapcraft-nontechnically-bilinear-viviana
error: Failed container creation:
- https://cloud-images.ubuntu.com/releases: No storage pool found. Please create a new storage pool.
This should show an error referring to LXD docs as well.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Superseded by #1771, merged as 1a7a4f7d0 to suppress tracebacks when LXD launch/init fails. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed in favor of #1771, merged as commit 1a7a4f7d0 to suppress tracebacks when LXD launch/init fails. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed in favor of canonical/snapcraft#1771, which was merged in commit 1a7a4f7d0 to suppress LXD launch/init tracebacks. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and superseded by pull request #1771, which provides a more direct fix for LXD launch failures and improved error handling. Reviewers were directed to evaluate the replacement pull request instead. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and superseded by pull request #1771. The maintainer directed contributors to continue the review and implementation efforts in the newer PR addressing LXD container launch error handling. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
canonical/snapcraft#1771
(confidence 100%)
The maintainer explicitly redirected the fix there; it merged as commit 1a7a4f7d0.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1771 lxd: suppress traceback when lxc launch / init fails | snapcraft | merged | Merged as commit 1a7a4f7d0: LXD launch/init failures now suppress Python tracebacks and rely on lxc's useful error output. | |
| #1641 lxd: catch CalledProcessError in _container_run | snapcraft | closed | Superseded by #1647, merged as 71f48bdc9, which improved LXD error handling and propagated exit codes without duplicating nested Snapcraft errors. |