feat(recovery): support provisioning write-access SSH keys in ic-recovery#8718
Merged
pierugo-dfinity merged 29 commits intomasterfrom Feb 27, 2026
Merged
Conversation
pierugo-dfinity
commented
Feb 11, 2026
…ugo/sev-recovery/ic-recovery-changes
d8efce5 to
3faefce
Compare
This reverts commit 3faefce.
pierugo-dfinity
commented
Feb 23, 2026
andrewbattat
approved these changes
Feb 23, 2026
eichhorl
approved these changes
Feb 26, 2026
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
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.
As part of SEV Recovery, recovery operators might eventually need to provision write-access SSH keys to patch the state. Registry changes were implemented in previous PRs (notably #7361), and orchestrator changes in #7265.
This PR implements the required changes in
ic-recovery. The tool now uses the newProposeToTakeSubnetOfflineForRepairsic-admincommand to provision an SSH key to a givenNodeId, that the tool asks for in theHaltstep. To help the recovery operator choose, this step will now print the heights of all nodes, next to theirNodeId. In contrast to regular recoveries, that first step will have to be ran on a local machine instead of directly on a node.Here is how the new
Haltstep would look like: