Repository navigation
fix: reconcile native service recovery before fleet updates - #23
Merged
Merged
Conversation
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.
Block new native updater work while a failed service job still needs recovery, and add a strict private receipt for verified restoration of the original IPMI container. The companion host CLI can create that receipt before adopting the newer controller; historical job and active-pointer bytes remain intact.
Submit, selection and worker checks revalidate the restored runtime and predecessor. A verified IPMI success retires its predecessor even if a later unrelated service rolls back. Failure diagnostics retain bounded phases without raw Engine errors or private configuration.
Validation: focused proxy and selector suites pass, including actual submit/worker partial-success, receipt durability and wrong-identity denial cases. Independent correctness and adversarial reviews are clear after the regression repair. Packaged Linux legacy bootstrap and live activation remain required; this PR does not update either site.