From 13b964b9d1c5baf3b227bf84c8de42bde376c205 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 13 Jun 2026 06:12:59 +0000 Subject: [PATCH] =?UTF-8?q?status(ghost):=20init=20phase=20=E2=80=94=20PR?= =?UTF-8?q?=20inventory=20done,=20post-proxy=20!testme=20triggered=20on=20?= =?UTF-8?q?PR#4?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR#4 (d88f5801) is the correct upgrade PR. All prior failures were pre-proxy-fix (2026-06-12). Fresh !testme triggered at 06:12:48Z on 2026-06-13 — post proxy /16 fix (05:38Z). PR#5 is a cfold probe artifact (close after M2); PR#3 superseded (close). --- machine-docs/BACKLOG-ghost.md | 16 +++++++++++ machine-docs/JOURNAL-ghost.md | 50 +++++++++++++++++++++++++++++++++++ machine-docs/REVIEW-ghost.md | 5 ++++ machine-docs/STATUS-ghost.md | 50 +++++++++++++++++++++++++++++++++++ 4 files changed, 121 insertions(+) create mode 100644 machine-docs/BACKLOG-ghost.md create mode 100644 machine-docs/JOURNAL-ghost.md create mode 100644 machine-docs/REVIEW-ghost.md create mode 100644 machine-docs/STATUS-ghost.md diff --git a/machine-docs/BACKLOG-ghost.md b/machine-docs/BACKLOG-ghost.md new file mode 100644 index 0000000..75d839f --- /dev/null +++ b/machine-docs/BACKLOG-ghost.md @@ -0,0 +1,16 @@ +# BACKLOG — phase ghost + +## Build backlog + +- [x] Inventory PR/branch/comment/build state — done (see STATUS-ghost.md) +- [ ] Trigger fresh post-proxy !testme on PR#4 (d88f5801) — IN PROGRESS +- [ ] Watch run, collect logs +- [ ] If GREEN: document infra-confounded prior failures; ensure cleanup; update PR; claim M1 +- [ ] If RED (recipe reason): make minimal fix (update_config.monitor/start_period); validate; claim M1 +- [ ] Close/mark superseded PRs: close PR#3 (superseded by #4); close PR#5 (cfold probe artifact) after M2 +- [ ] Claim M1 once build result is in and classification is documented +- [ ] Claim M2 once outcome is operator-ready and PR cleanup is done + +## Adversary findings + +(empty — Adversary fills this section) diff --git a/machine-docs/JOURNAL-ghost.md b/machine-docs/JOURNAL-ghost.md new file mode 100644 index 0000000..fd04764 --- /dev/null +++ b/machine-docs/JOURNAL-ghost.md @@ -0,0 +1,50 @@ +# JOURNAL — phase ghost + +## 2026-06-13T07:10Z — Phase start, PR inventory, fresh run triggered + +### PR inventory findings + +Three open PRs on recipe-maintainers/ghost: + +- **PR#4** (d88f5801): `chore: upgrade to 1.4.0+6.44.1-alpine` — the correct upgrade PR. + Had 4 pre-proxy-fix failures, all on 2026-06-12. The detailed failure in build 519 showed + MySQL 8.0→8.4 data-dir timing under load (Swarm UpdateStatus=paused) but the server + was under unusual load at the time (IPAM fix, Docker daemon restart, multiple concurrent builds). + The 3/3 budget was exhausted and then a 4th run was triggered at 21:51Z by the cfold/ghost agent, + also failing (pre-proxy-fix). + +- **PR#5** (d42d0f7c): `ci: cfold ghost green-head probe` — created by cfold/ghost agent as + sweep probe to verify the old-green head separately from the current PR#4 head regression. + Passed build 585 at 03:59Z on 2026-06-13 (BEFORE proxy fix at 05:38Z), so this pass was + on old infra. Not the correct PR — close after M2. + +- **PR#3** (720faa0b): `chore: upgrade to 1.3.0+6.43.1-alpine` — superseded by PR#4. Close. + +### Proxy fix status + +`docker network inspect proxy` shows subnet 10.10.0.0/16 — the /16 fix is in place. +pvfix completed at 05:38Z on 2026-06-13, pvcheck completed (M1+M2 PASS). + +### No resource leaks + +`docker stack ls`, `docker service ls`, `docker volume ls` — no ghost stacks or volumes. + +### Decision: trigger fresh post-proxy !testme on PR#4 + +The phase plan says "Do not count pre-proxy failures as current recipe evidence" and to run +one clean post-proxy `!testme`. All 4 failures on PR#4 were pre-proxy-fix. + +PR#5's build 585 passed the OLD head (d42d0f7c, ghost 6.44.0) but that was also pre-proxy-fix. +The upgrade path under test in PR#4 is different: upgrading to 1.4.0 (ghost 6.44.1 + mysql 8.4 +from mysql 8.0 base). This is the critical path. + +### Why the prior failures may be infra-confounded + +The diagnostic comment on PR#4 (build 519) specifically mentions "Docker daemon had just been +restarted (IPAM fix), multiple concurrent builds in progress, resulting in slower MySQL startup". +This is a direct load-induced timing issue, not a systematic recipe bug. The /16 proxy fix means +there's no longer VIP exhaustion risk, and we're not in the middle of an IPAM repair. + +However, the MySQL 8.0→8.4 data-dir upgrade timing is a real concern even without load pressure — +the update_config.monitor: 5s default may genuinely be too short for the migration. The fresh run +will clarify this. diff --git a/machine-docs/REVIEW-ghost.md b/machine-docs/REVIEW-ghost.md new file mode 100644 index 0000000..eb79269 --- /dev/null +++ b/machine-docs/REVIEW-ghost.md @@ -0,0 +1,5 @@ +# REVIEW — phase ghost + +(Adversary fills this file. Builder does not edit below this line.) + +--- diff --git a/machine-docs/STATUS-ghost.md b/machine-docs/STATUS-ghost.md new file mode 100644 index 0000000..4644463 --- /dev/null +++ b/machine-docs/STATUS-ghost.md @@ -0,0 +1,50 @@ +# STATUS — phase ghost (ghost upgrade re-evaluation) + +**Updated:** 2026-06-13T07:10Z +**Phase:** ghost +**Builder:** autonomic-bot + +--- + +## Current state: M1 IN PROGRESS — post-proxy fresh run triggered + +### PR inventory + +| PR | Title | Head | State | +|---|---|---|---| +| #4 | chore: upgrade to 1.4.0+6.44.1-alpine | d88f5801 | open — **CORRECT PR** | +| #5 | ci: cfold ghost green-head probe | d42d0f7c | open — sweep/probe artifact (do not merge; close after M2) | +| #3 | chore: upgrade to 1.3.0+6.43.1-alpine | 720faa0b | open — superseded by #4 | + +### Pre-proxy build history (PR#4, head d88f5801) + +| Build | Date | Result | Failure type | +|---|---|---|---| +| 515 | 2026-06-12T01:57Z | ❌ FAIL | unknown (first run after d88f5801 head push) | +| 517 | 2026-06-12T02:42Z | ❌ FAIL | unknown | +| 519 | 2026-06-12T03:03Z | ❌ FAIL | MySQL 8.0→8.4 timing / Swarm UpdateStatus=paused (under load from IPAM fix restart) | +| 557 | 2026-06-12T21:51Z | ❌ FAIL | unknown (4th run, pre-proxy-fix) | + +All four failures were **before the proxy /16 fix** (pvfix applied 2026-06-13T05:38Z). + +### Post-proxy run (PR#5 cfold probe, head d42d0f7c) + +| Build | Date | Result | Note | +|---|---|---|---| +| 559 | 2026-06-12T22:00Z | ❌ FAIL | pre-proxy-fix | +| 578 | 2026-06-13T02:22Z | ❌ FAIL | pre-proxy-fix | +| 585 | 2026-06-13T03:59Z | ✅ PASS | still pre-proxy-fix (proxy fixed 05:38Z) | + +### M1 action: fresh post-proxy !testme on PR#4 + +Triggered `!testme` on PR#4 (d88f5801) at ~2026-06-13T07:10Z — **awaiting build result**. + +Proxy is confirmed at 10.10.0.0/16 (healthy). No ghost stacks/volumes leaked. + +Gate: M1 IN PROGRESS — awaiting build result + +--- + +## Gate: M1 IN PROGRESS + +Awaiting fresh post-proxy CI run on PR#4 (d88f5801).