ssh.service could never start on a first boot: run the host-key generator before Debian's sshd -t - #930
Merged
Conversation
Drop-in ExecStartPre entries append after the main unit's, and Debian's ssh.service already runs 'sshd -t' as its own ExecStartPre. On a first boot /data/ssh is still empty, so the config test failed with 'no hostkeys available' before the generator ever ran — ssh.service could never start, and every _ssh leg of the KVM battery was dead (found by the battery on the merged tip; the wizard and stack were healthy, only SSH was down). Reset the ExecStartPre list, generate first, re-run the distro's own test; verify-image pins the three lines and their order. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
KVM-battery find on the merged tip (first live run of the #917 identity work): ssh.service failed on every start attempt in the guest, killing every
_sshbattery leg while the wizard and stack were healthy.Root cause: drop-in
ExecStartPreentries APPEND after the main unit's, and Debian's ssh.service already runssshd -t(a config test) as its own ExecStartPre. On a first boot/data/sshis still empty — the test fails with "no hostkeys available" before the generator ever runs, the unit dies, and every retry is identical.Fix: the drop-in resets the ExecStartPre list — generator first, then the distro's own test restated (frozen image, cannot drift). verify-image pins the reset line, both entries, and their order.
Battery rerun on this tip is queued (same run that found it). Ponytail: minimal.
🤖 Generated with Claude Code