Repository navigation
test(e2e): restore a lost store to the pinned revision after a tag move - #182
Merged
Merged
Conversation
maks3201
enabled auto-merge (squash)
October 14, 2026 07:57
|
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.
Adds one nightly/chaos e2e spec (
test/e2e/digest_restore_test.go) that proves pull-by-digest on Ollaya 0.13.0: promote laya:en (record the pinned digest), move the in-cluster mirror's laya:en tag to a different manifest, delete the stable store PVC + Pods after the stabilization window, and assert store recovery succeeds on the SAME revision, /api/ps on the recovered Pod reports the ORIGINAL digest, no failedRevision, and no UpstreamTagMoved / StorePrefetchFailed.The registry mirror (
hack/mirror/main.go) gains the by-digest manifest route (/v2/<ns>/<model>/manifests/sha256:<hex>, keyed on the sha256 of the SERVED urls-stripped bytes) and a MIRROR_TAG_MOVED mode that serves a byte-different-but-valid manifest for tag requests while the digest route keeps serving the original bytes.Depends on the digest-pull prefetch engine (default runtime 0.13.0): the spec is nightly/chaos (not in PR-required Tests/Lint) and only passes once that engine is on main. Verified locally on kind with the engine applied: 1 Passed, ~3.6m.