status(2): Q4.5 mattermost-lts P4 overlay authored, full-lifecycle run in flight
This commit is contained in:
@ -62,6 +62,13 @@ 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
|
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`).
|
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.6 discourse — BLOCKED/DEFERRED @2026-05-29.** Upstream recipe pins `bitnami/discourse:*` images
|
**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
|
that Docker Hub no longer serves (manifest unknown; swarm task Rejected "No such image"). Image exists
|
||||||
at `bitnamilegacy/discourse` but the install tier deploys the prev published version (also gone), so a
|
at `bitnamilegacy/discourse` but the install tier deploys the prev published version (also gone), so a
|
||||||
|
|||||||
Reference in New Issue
Block a user