Bad error report when the lxd instance is already running
Metadata
Current evaluation
A second craftapp pack in the same directory reports only that LXD failed to start when the managed instance is already running; the reproducer is clear, but maintainer triage is missing.
Suggested action: needs triage
Reason: The body provides an exact two-terminal reproducer, and the log identifies LXC's specific error: "The instance is already running." However, the issue has no labels, assignee, or substantive maintainer response beyond the synchronization bot; triage should also determine whether craft-application should translate this error or whether craft-providers should handle the concurrent-launch case.
Evaluated by: mr-cal-bot
Impact:
32
Quick Win:
17
Complexity:
37
Confidence:
88
Actionability:
82
Issue body
### Bug Description
I had a `pack` command crash for unrelated reasons, which left the lxd instance running. When running `craftapp pack` again I got the following error:
```
Launching managed ubuntu 22.04 instance...
Starting instance
Failed to start 'craftapp-hello-on-amd64-for-amd64-1'.
Full execution log: '/home/ubuntu/.local/state/craftapp/log/craftapp-20240703-093523.724743.log'
```
### To Reproduce
Run `craftapp pack`, and in another terminal run `craftapp pack` in the same directory again
### part yaml
```shell
n/a
```
### Relevant log output
```shell
2024-07-03 09:35:29.737 craft_providers.lxd.errors.LXDError: Failed to start 'craftapp-hello-on-amd64-for-amd64-1'.
2024-07-03 09:35:29.737 * Command that failed: 'lxc --project craftapp start local:craftapp-hello-on-amd64-for-amd64-1'
2024-07-03 09:35:29.737 * Command exit code: 1
2024-07-03 09:35:29.737 * Command standard error output: b'Error: The instance is already running\n'
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
17
Complexity:
37
Confidence:
88
Actionability:
82
|
needs triage | A second craftapp pack in the same directory reports only that LXD failed to start when the managed instance is already running; the reproducer is clear, but maintainer triage is missing. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
20
Complexity:
30
Confidence:
75
Actionability:
70
|
needs triage | Confusing error message when LXD instance is already running from a previous crash; user sees generic 'Failed to start' instead of helpful message about existing instance | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
24
Staleness:
75
Complexity:
40
Confidence:
60
Support Request:
10
|
needs triage | craftapp pack fails with a confusing 'Failed to start' LXDError when a prior crashed pack left the LXD instance running; the underlying lxc error 'The instance is already running' is not surfaced. Untriaged, no maintainer response, last activity 465 days ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
30
Confidence:
75
Support Request:
10
|
close stale | Bug report about a misleading error message when running 'craftapp pack' on an already running LXD instance. Issue is 748 days old with no maintainer resolution or further discussion since initial bot acknowledgment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Unhandled LXD error when instance is already running produces a confusing "Failed to start" message. Untriaged, unlabelled, and inactive for over two years. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.