Repository navigation
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
shiju-nv
force-pushed
the
fix/startup-conflict-recovery
branch
from
October 4, 2026 15:29
b4a4566 to
b2675ba
Compare
YasirBinMudassir
approved these changes
Oct 5, 2026
YasirBinMudassir
approved these changes
Oct 5, 2026
shiju-nv
force-pushed
the
fix/startup-conflict-recovery
branch
from
October 13, 2026 14:06
b7664dc to
20879b9
Compare
shiju-nv
changed the title
shiju-nv
marked this pull request as ready for review
October 13, 2026 14:08
|
This pull request has had no activity for 14 days and is now marked stale. |
github-actions
Bot
added
the
state:stale
|
Label |
shiju-nv
force-pushed
the
fix/startup-conflict-recovery
branch
from
November 2, 2026 14:46
3664c2e to
7c820f3
Compare
shiju-nv
changed the title
github-actions
Bot
removed
the
state:stale
A startup image-policy upload can read an empty sandbox baseline, then wait behind an operator's repair. When that upload commits, it can replace the repair. This preserves the management baseline and makes startup read fresh configuration after a write conflict. This covers a backfill selected before the competing repair. General fencing of delayed startup snapshots remains separate work. Signed-off-by: Shiju <shiju@nvidia.com>
shiju-nv
force-pushed
the
fix/startup-conflict-recovery
branch
from
November 3, 2026 11:46
7c820f3 to
e723e90
Compare
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.
Summary
A startup image-policy upload can read an empty sandbox baseline, then wait behind an operator's repair. When that upload commits, it can replace the repair. This preserves the management baseline and makes startup read fresh configuration after a write conflict.
This covers a backfill selected before the competing repair. General fencing of delayed startup snapshots remains separate work.
Related Issue
Related to #3784 and #3785, which addressed refused writes and stale rejection reports. This accepted-backfill race needs its own tracking issue before landing.
Changes
ABORTEDduring image-policy upload and filesystem-baseline write-back, preserving transport retries and the reconciliation budget.Release Notes
An operator's policy repair now survives a startup backfill that was already waiting to write.
Testing
The new gateway regression passes on the candidate and fails on main at
c92c2c798: main accepts the stale upload as revision 2. Scoped Clippy passes for the server and supervisor, including their test targets. Formatting, SPDX and documentation checks pass. E2E coverage is requested withtest:e2e; no final-head E2E pass is claimed yet.Checklist