The logs from the instance's charmcraft run are only retrieved if pack crashed
Metadata
Current evaluation
Fixed in canonical/charmcraft#726 (cc7d9ee0, merged as 6a05a07a): instance logs are now retrieved after both successful and failed charmcraft pack runs.
Resolution: closed resolved
Reason: PR #726 implemented the requested unconditional log retrieval and was merged into main as commit 6a05a07a.
Evaluated by: mr-cal-bot
No scores available.
Issue body
```
...
except subprocess.CalledProcessError as error:
capture_logs_from_instance(instance)
...
```
It should always capture them, because the pack may not "crash" but still may "fail" or do weird things. We always want to have "the last log" with complete details, because it will help a lot for bugs hard to reproduce (e.g., "just run `charmcraft pack` and this weird not reproducible thing happened"... the answer to that is "grab the last log, which has all the details")
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in canonical/charmcraft#726 (cc7d9ee0, merged as 6a05a07a): instance logs are now retrieved after both successful and failed charmcraft pack runs. | |
| stealth/space-bunny-alpha | — | closed resolved | Instance logs are now retrieved after both successful and failed pack runs via PR #726 (commit cc7d9ee0, merged in 6a05a07a). | |
| stealth/space-bunny-alpha | — | closed stale | Requested unconditional instance-log capture for charmcraft pack, but the issue closed without a linked fix or replacement after years of inactivity. | |
| stealth/space-bunny-alpha | — | closed stale | canonical/charmcraft#707 was closed without a linked PR or commit; the requested unconditional capture of instance pack logs was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requesting unconditional log capture on charmcraft pack failures was closed without resolution. No pull request or fix was implemented, indicating the change was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The request to always capture charmcraft pack logs regardless of crash status was abandoned. No fix or follow-up action was recorded. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution or an associated pull request. The request for unconditional log capture during charmcraft pack failures appears abandoned due to zero comments and no implementation. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#726
(confidence 99%)
Merged PR implementing retrieval of managed-instance logs on both success and failure.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #420 pack: fetch logs from managed instance on error (CRAFT-333) | charmcraft | merged | Merged in charmcraft#420 via fae2d7e8, adding managed-instance log capture on pack failures and per-run logs at /tmp/charmcraft.log. | |
| #701 `charmcraft pack` doesn't include all error output | charmcraft | closed | Missing charmcraft pack error output was fixed in Charmcraft 1.5 through improved managed-instance log retrieval; the reporter was using 1.4.0, so the issue was closed. |