snapcraft run uses one ssh key to create the image and another to log in
Metadata
Current evaluation
Inconsistent SSH key selection between snapcraft run and ubuntu-device-flash was closed without resolution. Zero comments indicate the report was abandoned or superseded without a fix.
Suggested action: —
No scores available.
Issue body
There's an inconsistency in how ssh keys are managed:
- ubuntu-device-flash will use the latest key
- snapcraft run will not (it will use the default key)
I think the key should be passed explicitly, and the selection logic should be the same.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Inconsistent SSH key selection between snapcraft run and ubuntu-device-flash was closed without resolution. Zero comments indicate the report was abandoned or superseded without a fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution due to inactivity. The SSH key inconsistency between snapcraft run and ubuntu-device-flash was abandoned, with no fix or implementation details provided. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1636979 snapcraft validate and sign-build are inconsistent when there are multiple keys | snapcraft (launchpad) | open | snapcraft validate uses the default signing key while sign-build shows a key-selection wizard when multiple keys exist; the two commands should behave consistently. Open since 2016, zero comments, no maintainer response. | |
| #1594876 snapcraft tests leave many ssh defunct processes | snapcraft (launchpad) | closed | Snapcraft tests generated defunct SSH processes. The report was closed without a documented fix, resolution, or linked pull request, indicating the issue was abandoned or resolved internally without tracking. |