admin
1637fa655d
gates / gates (push) Successful in 22s
The live proof: the box's own "send test notification" button pressed twice, 74 seconds apart, on demo-hp. Reporting `en` it produced "[Felhom] Test notification / Dear Customer, ..."; switched to `hu` it produced "[Felhom] Teszt értesítés / Kedves Ügyfél! ...", byte-for-byte the v0.117.0 literal. The operator's copy is identical in both, which is the half worth stating. R-583 (closed, hub v0.118.1): the test mail was the one customer mail that did not follow the language, and it is the mail an operator would use to CHECK that the language works. The surface you would use to check a feature is the one most worth checking first. R-584 (open, P2): five probe scripts from slice 2's releases B/C/D were still in the guest's /tmp carrying the controller password INLINE. The rule to delete them exists, was loaded, and was not followed three times running - so the rule is not the mechanism. All shredded; whether to rotate the shared demo password is the operator's call. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
26 lines
2.1 KiB
Plaintext
26 lines
2.1 KiB
Plaintext
=== BEFORE (rollback point):
|
|
gitea.dooplex.hu/admin/felhom-hub:0.117.0
|
|
sync=Synced health=Healthy rev=20aafc3dec2008f8f4697129bcf95bd354edef20
|
|
ROLLBACK LINE (written BEFORE the sync):
|
|
git revert the manifest tag to 0.117.0, commit, push, sync.
|
|
The two new COLUMNS stay and need no undo: v0.117.0 neither reads nor writes
|
|
them, both carry a DEFAULT, so every INSERT the old binary performs still
|
|
succeeds. SQLite cannot drop a column before 3.35 and the data is worth
|
|
keeping. Rolling back the IMAGE is the whole rollback.
|
|
=== AFTER:
|
|
sync=Synced health=Healthy rev=9167cf53afbc9cf62fdc92ca248d37a493e915e7
|
|
image=gitea.dooplex.hu/admin/felhom-hub:0.118.0
|
|
=== startup log:
|
|
2026/09/18 16:22:18 [INFO] Staleness checker initialized: 2 ok, 0 stale, 2 down (node_stale after 45m0s, node_down after 1h30m0s)
|
|
2026/09/18 16:22:18 [INFO] Host staleness checker initialized: 2 ok, 0 stale, 0 down (stale/down left unseeded → first Check emits; host_stale after 45m0s, host_down after 1h30m0s)
|
|
2026/09/18 16:22:20 [INFO] Host capability checker initialized: 2 ok, 0 degraded (degraded left unseeded → first Check emits)
|
|
2026/09/18 16:22:20 [INFO] Host leaf checker initialized: 2 host fingerprint(s) seeded
|
|
2026/09/18 16:22:20 [INFO] Host disk checker initialized: warn=90% crit=95%, 2 ok seeded, 0 already-breached left unseeded (first Check emits)
|
|
2026/09/18 16:22:20 [INFO] Storage fill checker initialized: warn=90% crit=95%, 6 ok seeded, 0 already-breached left unseeded, 2 root-backed excluded
|
|
2026/09/18 16:22:20 [INFO] Host mgmt-plane checker initialized: 0 host heal-state(s) seeded
|
|
2026/09/18 16:22:20 [INFO] Host OOB checker initialized: 0 host(s) seeded degraded
|
|
2026/09/18 16:22:20 [WARN] [offsite] tester-1: controller sends no last_success — staleness degraded to the last-ATTEMPT anchor (pre-v0.181.0 controller; a persistently failing tier will not go stale here until it upgrades)
|
|
2026/09/18 16:22:20 [INFO] Offsite checker initialized: fill warn=90% crit=95%, stale after 48h0m0s, 4 ok-seeded
|
|
2026/09/18 16:22:20 [INFO] Listening on :8080
|
|
2026/09/18 16:22:20 [INFO] deadline-check: next run at 2026-09-19 05:00 CEST (in 12h37m40s)
|