4.7 KiB
REPORT — release run 2026-10-29 (evening, attended): „Reboot guest" from the hub (D65 = A), R-1350, R-1346
The brief was dated Friday 2026-10-30; it started Thursday 15:54 CET. Part 2 (the stuck-controller decision, R-1344) needs the health log to 2026-10-30 07:00 UTC, so it is NOT in this run — it is the next session's first step.
Five lines
- The reboot button works, and its guards refused when they should: yes. On Tester 1, one press rebooted the guest (up after 67 s, the controller answered after 79 s); a press during an off-site run was refused („the controller is busy"); a second press inside the hour was refused. On the release builds: 66 s / 78 s, every app back, and the household's dashboard said „A Felhom ügyfélszolgálata 20:05-kor újraindította a dobozt."
- The stuck-controller decision: not taken yet (alarm only). The night log ends 2026-10-30 07:00 UTC. The logger runs (1 730 lines at 18:26 UTC, not read tonight); today's planned restarts and reboots are listed in R-1344 so tomorrow's reading leaves them out.
- R-1350 fixed: yes. After the operator's hold clear the app stayed stopped and no „app is not running" alarm came in 6.5 minutes (before: 30 s); the dead-app scan read „0 currently down".
- Where the vouch page's time goes: the hub's own database step of the save — 38.1 s of 38.3 s in „fleet check + save"; the registry took 135 ms, the page loads in 6 ms (in the cluster) / 65–255 ms (public name). ingress-nginx's default 60-s read timeout turns a save over 60 s into the 504. Not fixed tonight (it needs one more hub release).
- Released: hub 0.177.0, agent 0.170.0 (vouched), controller 0.349.0 (the global floor since 19:24 CET).
Versions, digests, CI by commit
| Repo | Commit | CI job | What |
|---|---|---|---|
| agent | ca15a31 |
2520, 2524 green | reboot_guest, its guards, the busy-file read, GET /guest/operator-reboot — 0.170.0 built from here (da8d12a0…, bundle 03f2ff64…, tag v0.170.0) |
| agent | 6578a8b |
2525 green | v0.170.0 heading; pinned.day0_agent = 0.170.0 |
| controller | b69e90b |
2521 green | busymark, the household line, R-1350 — rc.1 sha256:3bd08409… |
| controller | 94049a7 |
2526 green | v0.349.0 heading — 0.349.0 built from here (sha256:c5341883cd58410ea631fc0c76262d0902a731a24c1096df551e7d35df1ea877) |
| felhom.eu (hub) | 636022dc |
2522 green | the button, the 30-min reboot expiry, the slow-request line, the vouch timing — hub 0.177.0 (sha256:727eeec76bf728c00f9a7e645ad26fddff31addc5bca9f8465098e264eb90ef9) |
| felhom.eu | 8cc555be |
2523 green | manifest → 0.177.0 (Deployment/hub only) |
The close-out commits' CI is read at the end of the session.
Rows
- Before: 229. After: 228. Opened (1): R-1351 (FileBrowser boot race, P4). Closed (2): R-1349 (guest reboot from the hub), R-1350 (alarm after a hold clear). Updated: R-1346 (the numbers), R-1344 (planned events).
Observations
- FILED: R-1351 — at the release-build reboot two FileBrowser start paths ran
compose upin the same second; one logged two[ERROR]lines („container name already in use"); FileBrowser then ran healthy. Not seen on the first reboot an hour earlier. - FILED: R-1346 (numbers added) — beyond the vouch:
/apps25–30 s,/customers/tester-17–9 s,/system5.8 s in the access log of the last days. - NOT-A-FINDING: the off-site run's „not deployed — offsite push is unit-only" warnings on Tester 1 — existing, documented behaviour for apps with no recovery unit; unrelated to this run.
- NOT-A-FINDING: the agent mutation „no swap guard" survived — the reboot checked the swap twice (its own check and
jobBlocker's). The duplicate was removed andjobBlocker's check was proven by its own mutant. - NOT-A-FINDING: two controller mutants and one hub-side check first „failed" by not compiling — re-made so they compile; each then failed its test for the right reason.
Teardown
Machine: Tester 1 — the throwaway Gokapi removed through the product (no container, no app.yaml, no volume); the controller on 0.349.0 by the floor. 9202 runs rc.1 (not linked to the hub; stays until the next test). Host: nothing provisioned. Hub: no test customer or host; the per-box floors cleared after the 30-minute watch (clean: three boxes healthy on 0.349.0, 0 error/held/refused lines).
Docs
04 §6.1 [DESIGN] D65; 09 §3 decision 284; 03 [DESIGN] the reboot path; 05 [DESIGN] the button, the expiry, the
slow-request line; 08 [DESIGN] R-1350. The system poster: no fact changed (no machine, path, backup tier or time).
Evidence: documentation/audits/release-2026-10-29c/.