Repository navigation
Add daemon-driven HostOSReboot with restart-safe result reporting - #1015
Draft
hbc (bcho) with Copilot wants to merge 2 commits into
Draft
hbc (bcho) with Copilot wants to merge 2 commits into
hbc (bcho) with Copilot wants to merge 2 commits into
Conversation
Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Implement HostOSReboot in daemon agent for triggering rebooting from host
Add daemon-driven HostOSReboot with restart-safe result reporting
Oct 28, 2026
This branch has not been deployed
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.
Expose
HostOSRebootso the daemon can runrebooton the host and report the outcome after reconnecting, independently of cloud-provider or BMC power operations.InProgress.machineRef; keep external power controllers from claiming the operation. Refuse execution if the API does not persist the boot ID.Completion confirms an OS reboot, not Node readiness. Cordoning and draining remain caller responsibilities.