From 427b8ff8c71d3ac997803a85408cac6af90cf30f Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 20:55:31 +0000 Subject: [PATCH] =?UTF-8?q?status(2):=20ghost=20F2-14b=20blocked=20on=20ba?= =?UTF-8?q?ckup=20defect=20(abra=20omits=20mysql=20volume=20from=20snapsho?= =?UTF-8?q?t)=20=E2=80=94=20fix=20plan=20recorded,=20not=20claimed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/STATUS-2.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md index 6701b31..5998f23 100644 --- a/machine-docs/STATUS-2.md +++ b/machine-docs/STATUS-2.md @@ -92,11 +92,16 @@ DoD P2/P5/P6/P7/P8 broadly satisfied; remaining is P1 coverage of the above + Q5 ## In flight (@2026-05-30T19:3x — VETO-clearing cycle) Standing VETO on DONE (REVIEW-2 @16:22:07Z) requires: ghost + discourse + mumble all run **upgrade-to-latest** green with justified `compose.ccci.yml` overlays. Current cycle: -- **ghost F2-14b** — full run `/root/ccci-ghost-full4.log` IN FLIGHT (pid on cc-ci), reflecting the - CURRENT committed overlay `tests/ghost/compose.ccci.yml` (app+db `start_period:15m`, commit `3ca45c7`). - Verify on green: `ssh cc-ci 'tail -40 /root/ccci-ghost-full4.log'` → RUN SUMMARY deploy-count=1, - install/upgrade/backup/restore/custom ALL pass; base=1.1.1+6-alpine → PR-head `ae43ffe`. The prior - green full3 (17:23) used the pre-db-grace overlay → re-running to prove the committed state. +- **ghost F2-14b** — NOT claimed; blocked on a real recipe/harness backup defect P4 restore exposed. + full4 timed out (→ DEPLOY_TIMEOUT bumped 1200→2400, `4a160f6`). full5/6/7 then ran deploy-count=1, + install/upgrade/backup/custom PASS but **restore FAIL** (`ci_marker` absent post-restore). Root cause + (DECISIONS 2026-05-30 "ghost P4 restore dead-end", proven via restic snapshot inspection): `abra app + backup create` INTERMITTENTLY omits the mysql volume from the snapshot (db service still settling + after the upgrade-tier chaos redeploy that recreates it with the head's new backup labels/mount); + restore of a dump-less snapshot + a non-`pipefail` reimport hook silently loses the seeded row. 3rd + identical fail → stopped re-running. FIX (next): (1) harness — full-stack converge-wait before the + backup tier; (2) recipe-PR ghost#1 — `set -o pipefail` + fail-loud on missing dump. Then full green + incl upgrade-to-latest → claim. P4 caught a genuine data-loss path (the test is doing its job). - **discourse Q4.6** — overlay committed `845b86c` (`tests/discourse/{compose.ccci.yml,install_steps.sh}` + recipe_meta `UPGRADE_BASE_VERSION=0.7.0+3.3.1`, `CHAOS_BASE_DEPLOY`, `COMPOSE_FILE`). Run shape is now full `install,upgrade,backup,restore,custom` (upgrade-tier deferral WITHDRAWN per Adversary