Files
felhom.eu/documentation/audits/update-night-2026-09-21/batchCD.txt
T
admin 9c69b3ff07
gates / gates (push) Successful in 27s
Update night: Phases 2-4 evidence — both engines, the unattended HOLD, and five new findings
Evidence off the machine at the end of the phases that produced it (R-320). Teardown follows.

PHASE 2 — the two database engines, through the REAL Update button:
- MariaDB 11.6 -> 12.3 on nextcloud: PROVEN, and pressed through the button for the first time.
  All four SPIKE-r459 observables: the datadir's own record moved 11.6.2 -> 12.3.3; the engine
  itself says "already upgraded ... no need to run mariadb-upgrade again"; the entrypoint says
  "Major version upgrade detected ... Check required!" and then STARTED and FINISHED it (not the
  `skipped due to $MARIADB_AUTO_UPGRADE` line R-459 feared); and the engine took its own
  pre-upgrade backup, 631 905 B. The seeded Nextcloud account read back.
- PostgreSQL 16 -> 17 on docmost: FAILED exactly as R-463 predicted and nobody had measured.
  5.1 s to held; the pin named 17 while nothing ran; the restore brought it back in 29.1 s.
  The engine's REFUSAL LINE was destroyed by failAndHold before any probe could read it, so it
  was REPRODUCED INDEPENDENTLY with a control on every step (R-320).

PHASE 3 — the bad days. B1 produced THE UNATTENDED HOLD, which this project has never had: the
caller pressed once with nobody watching, the app held after 312.9 s, and passes 2 and 3 pressed
nothing. B2 put the pin back on a pull failure in 1.0 s. B3 refused `busy` six times. B4 showed
there is NO single-flight — 5 of 5 updates ran at once and all ended honest. B5 cut the power in
`backing-up` and the box recovered itself and said so. B7 refused under the 2 GB floor. B9 found
R-458's risk narrower than the row states.

PHASE 4 — every badge on the box is TRUE, and the held app answers all four of Q4's questions.

FINDINGS, five new and three corrections to existing rows. The one that matters: R-618 is P1 —
two templates name a health probe the app does not answer, and because the guarded update waits
on that same probe, a SUCCESSFUL update ends by STOPPING a working app. Measured: tandoor served
HTTP 200 on the new version at four samples across five minutes and was then stopped.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-21 22:13:57 +02:00

15 lines
1.2 KiB
Plaintext

grafana grafana/grafana:13.1.0 grafana/grafana:13.2.2 grafana other
vikunja vikunja/vikunja:2.3.0 vikunja/vikunja:2.6.0 tasks other
opengist ghcr.io/thomiceli/opengist:1.13 ghcr.io/thomiceli/opengist:1.15 gist other
papra ghcr.io/papra-hq/papra:26.6.1-rootless ghcr.io/papra-hq/papra:26.6.2-rootless papra other
romm rommapp/romm:5.0.0 rommapp/romm:5.3.0 arcade db-mariadb
home-assistant ghcr.io/home-assistant/home-assistant:2026.7.2 ghcr.io/home-assistant/home-assistant:2026.9.3 ha other
tandoor ghcr.io/tandoorrecipes/recipes:2.6.13 ghcr.io/tandoorrecipes/recipes:2.6.15 recipes db-postgres
mealie ghcr.io/mealie-recipes/mealie:v3.20.1 ghcr.io/mealie-recipes/mealie:v3.27.0 mealie db-postgres
vikunja vikunja/vikunja:2.3.0 vikunja/vikunja:2.6.0 tasks other
opengist ghcr.io/thomiceli/opengist:1.13 ghcr.io/thomiceli/opengist:1.15 gist other
romm rommapp/romm:5.0.0 rommapp/romm:5.3.0 arcade db-mariadb
mealie ghcr.io/mealie-recipes/mealie:v3.20.1 ghcr.io/mealie-recipes/mealie:v3.27.0 mealie db-postgres
opengist ghcr.io/thomiceli/opengist:1.13 ghcr.io/thomiceli/opengist:1.15 gist other
mealie ghcr.io/mealie-recipes/mealie:v3.20.1 ghcr.io/mealie-recipes/mealie:v3.27.0 mealie db-postgres