From 342c3b078f02c44eb89967764fea364ea4bfc234 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 01:41:37 +0100 Subject: [PATCH] status(2): Q4.5 mattermost recipe-PR #1 opened (pg_backup.sh restore fix), validation run in flight --- machine-docs/STATUS-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md index 817f97d..b04c7d8 100644 --- a/machine-docs/STATUS-2.md +++ b/machine-docs/STATUS-2.md @@ -62,7 +62,7 @@ deploy-count=1, clean teardown; the retry log proves the transient (POST 500 att attempt 2) and the synapse capture log shows the cause (restore-tier `DROP DATABASE FORCE` closed synapse's DB pool: `psycopg2.InterfaceError: connection already closed`). -**Q4.5 mattermost-lts โ€” P4 RESTORE BROKEN (recipe defect); recipe-PR needed @2026-05-30.** Full run +**Q4.5 mattermost-lts โ€” recipe-PR `recipe-maintainers/mattermost-lts#1` opened, validation run IN FLIGHT @2026-05-30** (`/root/ccci-mattermost-pr.log`, REF=4ca7f418). The recipe restore was a no-op (no `backupbot.restore.post-hook`); PR adds the coop-cloud `/pg_backup.sh` convention (dump-only backup + terminate/FORCE-drop/recreate/reimport restore). EXPECTED: restore tier `test_restore_returns_state` now GREEN. Original finding: Full run `/root/ccci-mattermost-full2.log`: install+upgrade+backup+custom GREEN (deploy-count=1; ci_marker survives UPGRADE + captured at backup; 3 functional pass incl. create_message_roundtrip ยง4.3), but **restore FAILS** โ€” `test_restore_returns_state`: `relation "ci_marker" does not exist` after restore.