recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

status/journal(2): Q4.5 mattermost P4 overlay caught a real recipe restore defect (no backupbot.restore.post-hook → DB not reimported); recipe-PR queued (immich pattern); node clean

Browse Source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
autonomic-bot
2026-05-30 01:30:19 +01:00
parent 012a477540
commit 11d6d82aad
2 changed files with 42 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
machine-docs/STATUS-2.md
View File

@ -62,12 +62,18 @@ 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 overlay authored, full-lifecycle run IN FLIGHT @2026-05-30**
(`/root/ccci-mattermost-full.log`). Added P4 data-integrity overlay (ops.py postgres ci_marker seed
+ test_install/upgrade/backup/restore). Recipe postgres-backed; its db backup is the whole PGDATA dir
(pg_dump pre-hook + backup.path=/var/lib/postgresql/data/) with NO explicit restore post-hook →
verifying empirically whether the file-level restore brings the ci_marker back (else recipe-PR like
immich). P3 present (create_message_roundtrip §4.3 + system_ping). NOT claimed.
**Q4.5 mattermost-lts — P4 RESTORE BROKEN (recipe defect); recipe-PR needed @2026-05-30.** 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.
ROOT CAUSE (recipe defect, same class as immich): the `postgres` service has a backup (pg_dump
pre-hook → postgres-backup.sql + `backup.path=/var/lib/postgresql/data/`) but **NO
`backupbot.restore.post-hook`**, and the file-level PGDATA restore doesn't take effect on the running
postgres → the DB keeps the post-drop state. FIX = recipe-PR adding a DB restore that reimports the
dump (immich pg_backup.sh pattern: terminate conns + drop+recreate + reimport postgres-backup.sql).
P4 overlay is correct + non-vacuous (it caught a real bug). NOT claimed — recipe-PR queued (BACKLOG-2
/ DEFERRED). Node clean. (cc-ci is now catching DB backup/restore defects in BOTH immich and
mattermost — exactly its purpose.)
**Q4.6 discourse — BLOCKED/DEFERRED @2026-05-29.** Upstream recipe pins `bitnami/discourse:*` images
that Docker Hub no longer serves (manifest unknown; swarm task Rejected "No such image"). Image exists