Files
felhom.eu/documentation/audits/evidence-spike-app-update-2026-09-01/phase6-01-deploy31.txt
T
admin 56c7e373a3
gates / gates (push) Successful in 18s
SPIKE: what an app update actually does, and which other paths do it too
THE GATE IS ANSWERED: YES. compose up -d upgrades an app whose compose file has
already moved, and the Restart button does it — 18.3s with a network pull when
the target image is absent, 0.5s when present, against a negative control that
did not even recreate the container. The boot reconciler does the same thing
unattended when an app fails to come back (bootrecon.go:269 -> StartStack).

AND ONE FEAR IS SMALLER THAN THE BRIEF CLAIMED: a plain power cut upgrades
nothing. Docker restores the old containers and the reconciler logs 'no
boot-orphaned apps (nothing to start)'.

AND ONE IS BIGGER: app data CANNOT be rolled back. Once a migration has run,
the old image refuses to start — Nextcloud: 'the version of the data (32.0.9.2)
is higher than the docker image version (31.0.14.1) and downgrading is not
supported'. 'Rollback' is the wrong word for this arc and is struck.

Phases 0-6 all run, on demo-hp (Tier 0, disposable). Phase 6 run on operator
confirmation. Peti's box was never contacted. No production code written in any
repo: felhom-controller is at 960d29b0612c before and after, tree clean, and
build/vet/test are green — run at the end to prove exactly that.

Register: R-438/439/440 updated with live evidence; R-441..R-445 opened
(restore-vs-sync conflict; remove_hdd_data inert with no paths.hdd_path, 128 MB
left behind; update reports success over a broken app; no fleet fstrim; hub
telemetry outlives the app). Capability map gains three measured rows. The
mechanism is written down in 02-controller-module-map.md as MEASURED BEHAVIOUR,
not [DESIGN] — the operator has not ruled. STATUS.md carries the one decision.

Five claims in the brief are named as wrong, including two of my own method.
2026-09-01 21:35:32 +02:00

20 lines
911 B
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
### Phase 6 — pin the stack to nextcloud:31.0.14-apache BEFORE deploying
2026-09-01T18:58:18Z
image: nextcloud:31.0.14-apache
image: mariadb:11.6
image: redis:7-alpine
### POST /api/stacks/nextcloud/deploy (file verified at nextcloud:31.0.14-apache above)
2026-09-01T18:58:40Z
{"ok":true,"message":"Telepítés elindítva – az állapot a kártyán követhető"}
HTTP=202 time=0.205833s
2026-09-01T18:58:40Z
2026-09-01T18:58:48Z
2026-09-01T18:59:10Z
2026-09-01T18:59:31Z nextcloud|nextcloud:31.0.14-apache|Created nextcloud-db|mariadb:11.6|Up 9 seconds (health: starting) nextcloud-redis|redis:7-alpine|Up 9 seconds (healthy)
>>> HEALTHY
2026-09-01T18:59:39Z nextcloud:31.0.14-apache|Up 6 seconds (health: starting)
2026-09-01T19:00:00Z nextcloud:31.0.14-apache|Up 28 seconds (health: starting)
2026-09-01T19:00:22Z nextcloud:31.0.14-apache|Up 49 seconds (healthy)
>>> nextcloud HEALTHY