fix: recover fsGroup-remounted execution partition startup without replay #466
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/partition-fsgroup-startup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
URGENT observed production startup outage during normal owning promotion, separate from model admission: Minerva harness CrashLoopBackOff14, Error Missing/unreadable partition. Read-only sidecar audit proved all865 referenced blobs exist, all865 exact SHA256 correct, all865 owned UID/GID1000, all865 mode0660 after fsGroup remount. Manifest retains849 execution records,1 event chunk,15 turn chunks. No missing/corrupt data and no ledger mutation/replay/reset performed.
Root cause: new PartitionedJson reader requires exact0600, unlike existing execution dependency fsGroup-compatible reader. Fix permits ONLY same-owner regular final-no-symlink600 or640/660 with group in actual kernel primary/supplementary membership; rejects unrelated groups, executable/world/special modes, corruption, symlinks. Cold load/qualification remains read-only, normal durable writer reseals0600 through opened FD and fsync. No authority/recovery/task/model/budget change.
11 new offline regressions plus existing partition/compatibility tests33pass; independent review PASS after supplementary-group case addressed. Regression filename local-* discovered by existing trusted mandatory Core workflow; no workflow changes. Full exact-head CI required before merge. Activation through normal image publication/owning GitOps only, never production chmod or ledger edits.
Follow-up before merge: current committed taskBookRef also points to fsGroup2770 directory/660 pages, so the same read-only hydration/normal-writer resealing fix now covers TaskBookStorage. Missing committed task-book directories/pages are wrapped to prevent ExecutionStore ENOENT empty-ledger fallback. Normal hydration no longer mkdirs/fsyncs task-book directories. Positive read-only actual PRIVATE COPY acceptance retains all849 executions and unchanged manifest dd6dd68f083d9760b60868a6df07bdcd9d55efc54fc2b03c2a8e004e8e771b13 with all dependency and current task-book pages. Earlier incomplete fixture with task-book pages absent exposed the empty-store defect; it was local only, fixed before activation, and is NOT an acceptance receipt. Current exact head
be15b23CI pending; earlier5a56a5bCI189 success is superseded, not evidence for this head.PI-REVIEW-RECEIPT
State: PASS
Head:
5a56a5b28cc6Summary: PASS: No P0 or P1 findings. One non-blocking race condition merits attention.
Findings: 1
Top findings:
PI-REVIEW-RECEIPT
State: PASS
Head:
be15b23eac01Summary: PASS: No P0 or P1 findings. The new permission checks introduce a non-blocking compatibility regression for previously accepted owner-read-only storage.
Findings: 1
Top findings:
PI-REVIEW-RECEIPT
State: PASS
Head:
1421d3d44ba8Summary: PASS — no P0 or P1 findings. One non-blocking edge case remains when staging an owner-read-only task-book page.
Findings: 1
Top findings: